You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a dedicated ci environment for running the tests on Codeship. Before starting all the tests, I explicitely set RAILS_ENV to ci. When running bundle exec rake parallel:create and bundle exec rake parallel:prepare, the databases in the correct environment are prepared. However, when running the tests with SPEC_OPTS='--tag ~js' bundle exec rake parallel:spec (I exclude Capybara integration tests), it executes some tests in the test environment. This is the output (I can detect the environment by the deprecation warning for dotenv):
Auto-loading of `.env.ci` will be removed in 1.0. See https://github.com/bkeepers/dotenv-deployment if you would like to continue using this feature.
4 processes for 82 specs, ~ 20 specs per process
Auto-loading of `.env.test` will be removed in 1.0. See https://github.com/bkeepers/dotenv-deployment if you would like to continue using this feature.
Is this a bug? Or do I miss something in order for all processes to run in the ci environment?
The text was updated successfully, but these errors were encountered:
Hmmm yeah I see. I also added looked at what the value is of ENV['RAILS_ENV'] in ParallelTests::RSpec::Runner.run_tests but it's set at the correct value. Now I'm wondering where that process is coming from that executes in the test environment...
I have a dedicated
ci
environment for running the tests on Codeship. Before starting all the tests, I explicitely setRAILS_ENV
toci
. When runningbundle exec rake parallel:create
andbundle exec rake parallel:prepare
, the databases in the correct environment are prepared. However, when running the tests withSPEC_OPTS='--tag ~js' bundle exec rake parallel:spec
(I exclude Capybara integration tests), it executes some tests in thetest
environment. This is the output (I can detect the environment by the deprecation warning fordotenv
):Is this a bug? Or do I miss something in order for all processes to run in the
ci
environment?The text was updated successfully, but these errors were encountered: