Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Test duration – parallelize? #9069
Closed
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I had another look at #8543 as I learned to fix some Unicode stream errors the other day. My current main obstacle is how long the tests run on Travis, no fun to make a PR and wait hours to see if it could be accepted. I could try and look into parallelizing the tests, like 20 at once, what would you think? (I'll ask first, since there was no reaction to said PR.)
Update: I'd also try and add some means to re-order the tests, so I could prioritize tests that made Travis fail last time. In the PR above, it looks like it crashed mainly due to a bug in nosetest, so if that one can be reproduced, all the other tests lapse and shouldn't delay that critical test.