Skip to content

[3.14] gh-126112: Fix test_os.TimerfdTests: use 10 ms resolution (GH-135681) #135704

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

Merged
merged 1 commit into from
Jun 19, 2025

Conversation

miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Jun 19, 2025

Use 10 ms for CLOCK_RES instead of 100 ms to tolerate slow buildbots.
(cherry picked from commit 5c25c88)

Co-authored-by: Victor Stinner [email protected]

…onGH-135681)

Use 10 ms for CLOCK_RES instead of 100 ms to tolerate slow buildbots.
(cherry picked from commit 5c25c88)

Co-authored-by: Victor Stinner <[email protected]>
Copy link

@newfadel newfadel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The change to use a 10 ms resolution instead of 100 ms for CLOCK_RES in test_os.TimerfdTests is a good improvement to make the tests more robust, especially for slower build environments. This addresses potential flakiness due to timing sensitivities. It's a positive step for test reliability. 😄

@vstinner vstinner merged commit 53b36e0 into python:3.14 Jun 19, 2025
50 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip news tests Tests in the Lib/test dir
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants