-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Set concurrency option to 1 when $TRAVIS = true #1060
Comments
I think that's specific to your tests. I use AVA with many projects and never experienced any problems with that. Did you figure it out? |
Maybe. I'm using AVA with Mockgoose and for endpoint testing. Without concurrency option set to 1, I've experienced inconsistent errors like that: I've read somewhere that Travis CI has a limit for multi processes, but I can't find it right now. This is the output: https://travis-ci.org/diegohaz/generator-rest/jobs/159648372#L331-L346 |
I solved this by updating the |
If I were to guess, copying the |
I don't think so. I'm currently creating symlinks instead of copying node_modules. I'll investigate it more, but I would like to see more examples with database mocking like Mockgoose. Creating a MongoDB instance, with all necessary models and indexes for each test (or even test file) seems to be a huge task. |
I'm actually doing something similar to this: Mockgoose/Mockgoose#3 (comment) |
Closing due to inactivity. @diegohaz feel free to reply back whenever you have time and we'll reopen the issue ;) |
I'm also having this issue on CircleCI... my |
I confim having ava running tests with Travis in serial mode can fix that kind of issue exited due to SIGKILL Resolved with ava --serial |
It seems like Travis CI doesn't handle multiple processes. I'm currently using this npm script to run tests:
"test": "[ \"$TRAVIS\" ] && c=1 || c=5; ava -c $c"
But it doesn't work on Windows. I'm looking for a cross-platform conditional statement solution, but I'm wondering if this condition should be made on AVA itself.
Reference: diegohaz/rest#11
The text was updated successfully, but these errors were encountered: