Sorry, something went wrong.
|
Hi @iritkatriel and thanks for taking a look at this. I have merged all test conflicts and polished the implementation a little, since the PR was 3 years and unittest code changed in the meantime. |
Sorry, something went wrong.
|
@LiteApplication thanks for approving. Merging. |
Sorry, something went wrong.
|
@giampaolo @LiteApplication doesn't appear to be a regular Python reviewer, is it no problem to merge? |
Sorry, something went wrong.
|
Hidden buildbot failure was for test_asyncio. I presume unrelated since random test_asyncio failures are unfortunately routine. |
Sorry, something went wrong.
Sorry, something went wrong.
|
@eggplants wrote: @giampaolo @LiteApplication doesn't appear to be a regular Python reviewer, is it no problem to merge? Sorry, I didn't realize that. This was an old PR that unfortunately never received much attention, so it stayed idle for a long time and I occasionally updated it to fix merge conflicts. When I finally saw an approval I was just happy to see it and merged it without further checking. FWIW, I went through these changes multiple times over the last 4 years: I'm confident that the changes introduced in here are OK and are fully retro compatible (this probably was the most sensitive part to consider). |
Sorry, something went wrong.
|
Anyway, I am glad this feature has finally been merged. Thank you @giampaolo -san. |
Sorry, something went wrong.
|
Here's a nose issue related to this PR's retro-compatibility: nose-devs/nose2#569. |
Sorry, something went wrong.
Adds cmdline option to show unit-tests durations + summary of the slowest ones, see https://bugs.python.org/issue4080.
Top 5 slowest ones:
All + individual elapsed time:
https://bugs.python.org/issue4080