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
priority
in sched.scheduler
is not sufficiently tested
#90808
Comments
Right now there only a single test to ensure cpython/Lib/test/test_sched.py Lines 90 to 97 in fea7290
It looks like it is not enough. Why?
This test does not actually test different priorities. It only tests that a direct one works correctly. But, this might be a pure coincidence that numbers match. They are spawned in this particular order. What if there are equal numbers? Like I propose adding more examples to this test. PR is on its way. |
…onGH-31144) (cherry picked from commit 57463d4) Co-authored-by: Nikita Sobolev <mail@sobolevn.me>
…onGH-31144) (cherry picked from commit 57463d4) Co-authored-by: Nikita Sobolev <mail@sobolevn.me>
(cherry picked from commit 57463d4) Co-authored-by: Nikita Sobolev <mail@sobolevn.me>
(cherry picked from commit 57463d4) Co-authored-by: Nikita Sobolev <mail@sobolevn.me>
Can this be closed? |
yes |
sobolevn commentedFeb 5, 2022
test_sched.test_priority
#31144Note: 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: