New submission from Matthias Klose <d...@debian.org>:
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. ---------- components: Tests messages: 415027 nosy: doko priority: normal severity: normal status: open title: test_multiprocessing_fork running without any timeout _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue46999> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
