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 upTravis CI: Identify our ten slowest pytests #2350
Conversation
https://howchoo.com/g/mtblodnjzjc/how-to-measure-unit-test-execution-times-in-pytest helps us to find the individual tests that are slowing down our Travis CI checks.
|
@cclauss. Sure |
PR #2305 which added the file problem_34 (which takes the longest time) did not pass all the tests. Here is the log of the test which failed. |
|
The idea is to not lower the reader’s confidence that the code will work as expected. Best: speed up the implementation and keep the test. |
I can speed up the implementation. Shall I start a PR now? |
|
Please don’t wait for permission... If you see something that should be done then do it. |
cclauss commentedAug 25, 2020
•
edited
https://howchoo.com/g/mtblodnjzjc/how-to-measure-unit-test-execution-times-in-pytest helps us to find the individual tests that are slowing down our Travis CI checks.
@Kush1101 Given that our slowest test is taking 36 seconds on every pull request, would you be willing to look at that test and see if you can speed things up? Also, the third test.
Describe your change:
Checklist:
Fixes: #{$ISSUE_NO}.