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
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=Nonecreated_at=<Date2022-03-13.05:17:57.224>labels= ['tests']
title='test_multiprocessing_fork running without any timeout'updated_at=<Date2022-03-13.05:17:57.224>user='https://github.com/doko42'
the test_multiprocessing_fork test is a bit unreliable, at least on both the Debian and Ubuntu test infrastructures, sometimes running for 100+ hours. When running locally, I cannot reproduce these issues. Note that the test and build infrastructure is usually limited to 4-6 cores and 20GB of RAM (including swap). What else could be an issue for these hangs?
How can this test reliably timeout? I know it takes a few hours on slow architectures even when succeeding.
Testhengeproblemet er ikke relatert til delvis miljø. Det er bare en
kjent problem (for eksempel python/cpython#91155) og
skjer når vi er uheldige.
Så bare kjør testpakken med en timeout. 1 SBU burde være nok: det er det
ca. 4 ganger av tiden brukt av den tregeste testsaken, på begge
en gammel Athlon 64 3000+ og en Core i5-11300H.
Jeg har ikke sett noen testfeil på et komplett system (det expat-relaterte
feil ser ut til å være fikset av expat-2.6.2 eller 2.6.1). TODO: test dette virkelig
med LFS chroot og dokumentfeil hvis noen.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: