-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
test_monitoring
has duplicated tests
#106193
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
Comments
No, they cannot be just deleted, because they test different things. |
Introduced in b32a075#diff-15fb0cb29709c04c449bacd69e4ab2208372424d8390c26258eb83b2363c3cf1 Looks like it never had parts that are missing right now. |
Please see PR #109139. |
markshannon
pushed a commit
that referenced
this issue
Oct 12, 2023
hugovk
added a commit
to hugovk/cpython
that referenced
this issue
Oct 15, 2023
…toring` (pythonGH-109139) (cherry picked from commit ea530f2) Co-authored-by: Hugo van Kemenade <[email protected]>
hugovk
added a commit
that referenced
this issue
Oct 15, 2023
Glyphack
pushed a commit
to Glyphack/cpython
that referenced
this issue
Sep 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Based on python/core-workflow#505 by @hugovk
Before rename:
Ran 49 tests in 0.014s
After rename:
Based on the missing runtime parts in these tests, we can just remove the first two ones, I guess.
Both of these tests were introduced in 411b169 by @markshannon
Linked PRs
test_monitoring
#109139test_monitoring
(GH-109139) #110897The text was updated successfully, but these errors were encountered: