Skip to content

gh-110695: test_asyncio uses 50 ms for clock resolution #110952

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Oct 17, 2023
Merged

gh-110695: test_asyncio uses 50 ms for clock resolution #110952

merged 1 commit into from
Oct 17, 2023

Conversation

vstinner
Copy link
Member

@vstinner vstinner commented Oct 16, 2023 •
edited by bedevere-app bot
Loading

Before utils.CLOCK_RES constant was added (20 ms), test_asyncio already used 50 ms.

@vstinner
pythongh-110695: test_asyncio uses 50 ms for clock resolution
1fbd24a 
Before utils.CLOCK_RES constant was added (20 ms), test_asyncio
already used 50 ms.
@vstinner vstinner added tests Tests in the Lib/test dir topic-asyncio needs backport to 3.11 only security fixes needs backport to 3.12 only security fixes labels Oct 16, 2023
@bedevere-app bedevere-app bot mentioned this pull request Oct 16, 2023
Closed
@vstinner
Copy link
Member Author

Before utils.CLOCK_RES constant was added (20 ms), test_asyncio already used 50 ms.

See commit db0a258.

@vstinner
Copy link
Member Author

cc @kumaraditya303

@vstinner vstinner merged commit 9a9fba8 into python:main Oct 17, 2023
@vstinner vstinner deleted the test_asyncio_clock_res branch October 17, 2023 09:34
@miss-islington-app
Copy link

Thanks @vstinner for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11, 3.12.
🐍🍒⛏🤖

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Oct 17, 2023
@vstinner @miss-islington
pythongh-110695: test_asyncio uses 50 ms for clock resolution (python…
89cc6a8 
…GH-110952)

Before utils.CLOCK_RES constant was added (20 ms), test_asyncio
already used 50 ms.
(cherry picked from commit 9a9fba8)

Co-authored-by: Victor Stinner <[email protected]>
miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Oct 17, 2023
@vstinner @miss-islington
pythongh-110695: test_asyncio uses 50 ms for clock resolution (python…
e6b2b5e 
…GH-110952)

Before utils.CLOCK_RES constant was added (20 ms), test_asyncio
already used 50 ms.
(cherry picked from commit 9a9fba8)

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

bedevere-app bot commented Oct 17, 2023

GH-110970 is a backport of this pull request to the 3.12 branch.

@bedevere-app bedevere-app bot removed the needs backport to 3.12 only security fixes label Oct 17, 2023
@bedevere-app
Copy link

bedevere-app bot commented Oct 17, 2023

GH-110971 is a backport of this pull request to the 3.11 branch.

@bedevere-app bedevere-app bot removed the needs backport to 3.11 only security fixes label Oct 17, 2023
@vstinner
Copy link
Member Author

Merged. Thanks for the review @kumaraditya303.

vstinner added a commit that referenced this pull request Oct 17, 2023
@miss-islington @vstinner
[3.11] gh-110695: test_asyncio uses 50 ms for clock resolution (GH-11…
ae495de 
…0952) (#110971)

gh-110695: test_asyncio uses 50 ms for clock resolution (GH-110952)

Before utils.CLOCK_RES constant was added (20 ms), test_asyncio
already used 50 ms.
(cherry picked from commit 9a9fba8)

Co-authored-by: Victor Stinner <[email protected]>
vstinner added a commit that referenced this pull request Oct 17, 2023
@miss-islington @vstinner
[3.12] gh-110695: test_asyncio uses 50 ms for clock resolution (GH-11…
9aa8993 
…0952) (#110970)

gh-110695: test_asyncio uses 50 ms for clock resolution (GH-110952)

Before utils.CLOCK_RES constant was added (20 ms), test_asyncio
already used 50 ms.
(cherry picked from commit 9a9fba8)

Co-authored-by: Victor Stinner <[email protected]>
aisk pushed a commit to aisk/cpython that referenced this pull request Feb 11, 2024
@vstinner @aisk
pythongh-110695: test_asyncio uses 50 ms for clock resolution (python…
c548279 
…#110952)

Before utils.CLOCK_RES constant was added (20 ms), test_asyncio
already used 50 ms.
Glyphack pushed a commit to Glyphack/cpython that referenced this pull request Sep 2, 2024
@vstinner @Glyphack
pythongh-110695: test_asyncio uses 50 ms for clock resolution (python…
21ec40b 
…#110952)

Before utils.CLOCK_RES constant was added (20 ms), test_asyncio
already used 50 ms.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@kumaraditya303 kumaraditya303 kumaraditya303 approved these changes

@1st1 1st1 Awaiting requested review from 1st1 1st1 is a code owner

@asvetlov asvetlov Awaiting requested review from asvetlov asvetlov is a code owner

@gvanrossum gvanrossum Awaiting requested review from gvanrossum

@willingc willingc Awaiting requested review from willingc willingc is a code owner

Assignees
No one assigned
Labels
skip news tests Tests in the Lib/test dir topic-asyncio
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@vstinner @kumaraditya303