GeezerVison is showing github.com — gh-109162: libregrtest: move code around by vstinner · Pull Request #109253 · python/cpython
Conversation
vstinner
commented
Sep 11, 2023
•
edited by bedevere-bot
Loading
Uh oh!
There was an error while loading. Please reload this page.
- Move Regrtest.display_header() to utils.py.
- Move cleanup_temp_dir() to utils.py.
- Move list_cases() to findtests.py.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
vstinner
commented
Sep 11, 2023
•
edited
Loading
Uh oh!
There was an error while loading. Please reload this page.
|
Strange, test_regrtest.test_huntrleaks() failed on Windows x64, but only test_huntrleaks(): test_huntrleaks_mp() passed for example whereas it's basically the same test run in a worker process.
- expected:
test_regrtest_huntrleaks leaked [1, 1, 1] references, sum=3
- got:
test_regrtest_huntrleaks leaked [1, 1, 9] references, sum=11
I don't know where these +8 references are coming from.
I suppose that it's random failures. Maybe related to an internal Python cache.
FAIL: test_huntrleaks (test.test_regrtest.ArgsTestCase.test_huntrleaks)
----------------------------------------------------------------------
Traceback (most recent call last):
File "D:\a\cpython\cpython\Lib\test\test_regrtest.py", line 1060, in test_huntrleaks
self.check_huntrleaks(multiprocessing=False)
File "D:\a\cpython\cpython\Lib\test\test_regrtest.py", line 1057, in check_huntrleaks
self.check_leak(code, 'references', multiprocessing=multiprocessing)
File "D:\a\cpython\cpython\Lib\test\test_regrtest.py", line 1039, in check_leak
self.assertIn(line2, output)
AssertionError: 'test_regrtest_huntrleaks leaked [1, 1, 1] references, sum=3\n' not found in '0:00:00 Run tests sequentially\n0:00:00 [1/1] test_regrtest_huntrleaks\nbeginning 9 repetitions\n123456789\n.........\ntest_regrtest_huntrleaks leaked [1, 1, 9] references, sum=11\ntest_regrtest_huntrleaks leaked [1, 1, 1] memory blocks, sum=3\ntest_regrtest_huntrleaks failed (reference leak)\n\n== Tests result: FAILURE ==\n\n1 test failed:\n test_regrtest_huntrleaks\n\nTotal duration: 496 ms\nTotal tests: run=1\nTotal test files: run=1/1 failed=1\nResult: FAILURE\n'
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Strange, test_regrtest.test_huntrleaks() failed on Windows x64
I cannot reproduce the issue on Windows or Linux with ./python -m test -v test_regrtest -j1 --forever. The test passed 3-4 times on each OS (I didn't wait longer).
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
* Move Regrtest.display_header() to utils.py.
* Move cleanup_temp_dir() to utils.py.
* Move list_cases() to findtests.py.
|
I rebased my PR on main to get "gh-107219: Fix concurrent.futures terminate_broken() (#109244)" fix. test_concurrent_futures hanged twice on the Windows x64 job.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
|