-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TEST_ENV_NUMBER value incorrect for first process #12
Comments
Hi @scottbartell, Ref: parallel_tests --first-is-1 The random blog post that describes a similar problem. Let me know if it solves the problem you've encountered. PS. Can you tell me about your usage workflow of |
The solution if you want to use |
@louim Yes, please update the documentation in PR. |
@louim have you already made request? It seems, repo is missing information about |
@Mayurifag sorry, I totally forgot to do a PR. I'll try to draft one this week, but if you want to create one, go ahead! |
if I understand correctly, all we're missing here is an update to the README to mention the |
@gutoarraes i can confirm that @louim suggestion works for us i think it should be part of the docs imo |
The
TEST_ENV_NUMBER
env var is being set to1
for the first process whenparallel_tests
expects it to be blank. This is causing issues becauseparallel_tests
doesn't create a database whereTEST_ENV_NUMBER=1
when you runrake parallel:setup
.Here's where
TEST_ENV_NUMBER
is being set to1
: https://github.com/serpapi/turbo_tests/blob/master/lib/turbo_tests/runner.rb#L112Here's the docs for
parallel_tests
: https://github.com/grosser/parallel_tests#add-to-configdatabaseymlI'd be happy to address this but I'm curious if we think
turbo_tests
should be changed to set the value to empty string likeparallel_tests
expects or if we should figure out if we can configureparallel_tests
to use the value1
for the first process and just add some documentation on how to do that?The text was updated successfully, but these errors were encountered: