Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

<not running> console spam when running tests #127152

Closed
colesbury opened this issue Nov 22, 2024 · 1 comment
Closed

<not running> console spam when running tests #127152

colesbury opened this issue Nov 22, 2024 · 1 comment
Labels
tests Tests in the Lib/test dir

Comments

@colesbury
Copy link
Contributor

Since gh-126855, running tests, such as via make test now prints out lots of lines like:

0:00:44 load avg: 17.49 [477/480] test.test_multiprocessing_forkserver.test_processes passed (36.9 sec) -- running (82): <not running> (44.1 sec), <not running> (34.7 sec), <not running> (39.3 sec), <not running> (38.9 sec), <not running> (34.0 sec), <not running> (36.8 sec), <not running> (38.7 sec), <not running> (42.4 sec), <not running> (44.3 sec), <not running> (44.6 sec), <not running> (44.6 sec), <not running> (33.6 sec), test.test_multiprocessing_spawn.test_processes (43.9 sec), <not running> (34.1 sec), <not running> (33.9 sec), <not running> (43.7 sec), <not running> (44.6 sec), <not running> (44.1 sec), <not running> (37.6 sec), <not running> (36.7 sec), <not running> (44.6 sec), <not running> (43.8 sec), <not running> (35.9 sec), <not running> (38.4 sec), <not running> (36.3 sec), test.test_concurrent_futures.test_wait (44.1 sec), <not running> (44.1 sec), <not running> (43.9 sec), <not running> (44.5 sec), <not running> (34.6 sec), <not running> (43.3 sec), <not running> (42.9 sec), <not running> (37.7 sec), <not running> (34.5 sec), <not running> (33.6 sec), <not running> (35.2 sec), <not running> (36.9 sec), <not running> (33.6 sec), <not running> (33.4 sec), <not running> (37.1 sec), <not running> (33.4 sec), <not running> (34.0 sec), <not running> (38.1 sec), <not running> (40.5 sec), <not running> (40.0 sec), <not running> (39.9 sec), <not running> (43.9 sec), <not running> (44.5 sec), <not running> (44.5 sec), <not running> (39.0 sec), <not running> (34.2 sec), <not running> (35.6 sec), <not running> (36.3 sec), <not running> (43.0 sec), <not running> (33.5 sec), <not running> (35.5 sec), <not running> (43.5 sec), <not running> (42.5 sec), <not running> (40.8 sec), <not running> (33.7 sec), <not running> (39.5 sec), test_subprocess (34.9 sec), <not running> (33.4 sec), <not running> (35.2 sec), <not running> (44.0 sec), <not running> (35.8 sec), <not running> (44.0 sec), <not running> (41.6 sec), <not running> (34.0 sec), <not running> (36.2 sec), <not running> (38.9 sec), <not running> (40.5 sec), <not running> (43.2 sec), <not running> (33.6 sec), <not running> (36.7 sec), <not running> (39.2 sec), <not running> (34.8 sec), <not running> (37.8 sec), <not running> (39.3 sec), <not running> (34.3 sec), <not running> (34.2 sec), <not running> (34.4 sec)

I think the <not running> prints are unintentional.

cc @sobolevn

@colesbury colesbury added the tests Tests in the Lib/test dir label Nov 22, 2024
@vstinner
Copy link
Member

I wrote #127153 to fix the regression.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tests Tests in the Lib/test dir
Projects
None yet
Development

No branches or pull requests

2 participants