Repository navigation
Add the --duration option to the test suite #119050
Description
Activity
Why not reusing the JUnit output?
Why not reusing the JUnit output?
JUnit cannot be used in a "hunt refleaks" mode. Although, using JUnit for this purpose would be great, but I do not see an easy solution to making it work with the "hunt refleaks" mode :(
JUnit cannot be used in a "hunt refleaks" mode. Although, using JUnit for this purpose would be great, but I do not see an easy solution to making it work with the "hunt refleaks" mode :(
We should write JUnit data into a file, and then load the file to write the XML. Not store these data into memory.
- added 5 commits that reference this issue
on May 18, 2024 JUnit cannot be used in a "hunt refleaks" mode. Although, using JUnit for this purpose would be great, but I do not see an easy solution to making it work with the "hunt refleaks" mode :(
It's now supported! Is it enough for your use case?
JUnit cannot be used in a "hunt refleaks" mode. Although, using JUnit for this purpose would be great, but I do not see an easy solution to making it work with the "hunt refleaks" mode :(
It's now supported! Is it enough for your use case?
Yes, it is! Thanks Victor!
Feature or enhancement
Proposal:
I propose adding a new option
--durationto our test suite. This would print the duration of each test that has run during the test suite, to the file that the user provides.So actual use case looks like that:
./python.exe -m test --duration tmp/stats -R 3:3It's can be useful as the
--slowestoption, which already exists.Has this already been discussed elsewhere?
This is a minor feature, which does not need previous discussion elsewhere
Links to previous discussion of this feature:
No response
Linked PRs
--durationoption for the test suite CLI #119051