You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add the --duration option to the test suite #119050
I propose adding a new option --duration to 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:3
It's can be useful as the --slowest option, which already exists.
Has this already been discussed elsewhere?
This is a minor feature, which does not need previous discussion elsewhere
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.
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?
Activity
vstinner commentedon May 15, 2024
Why not reusing the JUnit output?
Eclips4 commentedon May 15, 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 :(
vstinner commentedon May 17, 2024
We should write JUnit data into a file, and then load the file to write the XML. Not store these data into memory.
pythongh-119050: Add type hints to libregrtest/results.py
pythongh-119050: Add type hints to libregrtest/results.py
pythongh-119050: Add XML support to libregrtest refleak checker
pythongh-119050: Add XML support to libregrtest refleak checker
gh-119050: Add type hints to libregrtest/results.py (#119144)
pythongh-119050: Add type hints to libregrtest/results.py (pythonGH-1…
pythongh-119050: Add type hints to libregrtest/results.py (pythonGH-1…
[3.13] gh-119050: Add type hints to libregrtest/results.py (GH-119144) (
[3.12] gh-119050: Add type hints to libregrtest/results.py (GH-119144) (
gh-119050: Add XML support to libregrtest refleak checker (#119148)
pythongh-119050: Add XML support to libregrtest refleak checker (pyth…
pythongh-119050: Add XML support to libregrtest refleak checker (pyth…
vstinner commentedon May 20, 2024
It's now supported! Is it enough for your use case?
Eclips4 commentedon May 20, 2024
Yes, it is! Thanks Victor!
[3.13] gh-119050: Add XML support to libregrtest refleak checker (GH-…
[3.12] gh-119050: Add XML support to libregrtest refleak checker (#11…
pythongh-119050: Add type hints to libregrtest/results.py (python#119144
pythongh-119050: Add XML support to libregrtest refleak checker (pyth…