Separate slower running integration tests to run in parallel#117
Separate slower running integration tests to run in parallel#117eb8680 merged 5 commits intopyro-ppl:devfrom neerajprad:travis_parallel_matrix
Conversation
| - pip install torchvision | ||
|
|
||
| script: | ||
| - PYTHONPATH=$PWD:$PYTHONPATH pytest -s --cov=pyro |
There was a problem hiding this comment.
I find the the -v flag helpful (or -vs) to see the name of each test as it is run.
There was a problem hiding this comment.
Nice. will make the change.
|
|
||
| script: | ||
| - PYTHONPATH=$PWD:$PYTHONPATH pytest -s --cov=pyro | ||
| - flake8 && PYTHONPATH=$PWD:$PYTHONPATH pytest -s --cov=pyro tests/$TEST_DIRECTORY |
There was a problem hiding this comment.
Why not just separate lines
script
- flake8
- pytest ...
There was a problem hiding this comment.
Just updated in the description above. I think this will run the tests even if lint fails. Ideally, we should just mark the build as failed, and wait for the dev to fix this before running the expensive test suite. Thoughts?
|
The faster unit tests finish within 20 mins; and the longer integration tests are still running. There are still some statistical errors, which we should rectify in the unit tests, at least (not for this PR).
|
Looks like Travis has a beta feature, Build Stages, that could be useful here. |
|
@eb8680 - will quickly try out the Build Stages feature. |
|
@eb8680 - This seems to work well. I think we can go with this and add more parallelization within each of the stages later. It will be great if we can finish off the fast testing (i.e. everything up to unit tests) within 10 minutes. |
Changes to .travis.yml: