Downgraded skips in tests#6716
Conversation
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (27)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including You can disable this status message by setting the 📝 WalkthroughWalkthroughA single test identifier was added to the Windows environment-polluting tests list in the CI workflow configuration, expanding the set of tests flagged as environment-polluting for Windows CI runs. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Sorry, something went wrong.
5ac99cf to
770c867
Compare
January 12, 2026 21:17
|
Double check tests in |
Sorry, something went wrong.
|
Note to self: testing if, given the new timeout, whether timeouts count as failures, or errors (expectedFailure vs skips) |
Sorry, something went wrong.
fanninpm
left a comment
There was a problem hiding this comment.
A few extra things besides these inline comments:
- for
Lib/test/test_zipfile/test_core.py, we might need to add support for thatshift_jisencoding. - for
Lib/test/bdb.py, @youknowone Is #6626 going to fix the tests that are decorated?
Sorry, something went wrong.
33cead3 to
1c62ce3
Compare
January 13, 2026 05:44
ShaharNaveh
left a comment
There was a problem hiding this comment.
Overall it looks great!
Minor nitpicks about some added code that we can delete.
TYSM!!!
Sorry, something went wrong.
fa5ef2e to
ea760c8
Compare
January 13, 2026 23:42
youknowone
left a comment
There was a problem hiding this comment.
Thank you so much! You seem to find many outdated skips in our test code.
Please make sure unskipped tests are not actually flaky. Running multiple times of them will be helpful.
Sometimes they are flaky on specific platforms. I will run the entire CI multiple times once this is done.
Sorry, something went wrong.
8ee84ea to
ed6dc56
Compare
January 14, 2026 02:37
|
@youknowone It should be ok to rereview/run the CI/CD tests. Like I said, there seem to be intermittent issues with |
Sorry, something went wrong.
80a5f8b to
559d35d
Compare
January 14, 2026 11:51
|
You’re right. those are making it hard to see the actual results of this test. I’ll fix that and run it again. |
Sorry, something went wrong.
559d35d to
8a5c49f
Compare
January 14, 2026 23:38
8a5c49f to
6a3932d
Compare
January 15, 2026 05:30
|
the failure looks like unrelated |
Sorry, something went wrong.
youknowone
left a comment
There was a problem hiding this comment.
@terryluan12 Thank you so much! I wish your awesome script to be integrated to our tools soon. Unskipping tests is not a 5 seconds task, you made it in great way. Thanks!
No issue for 6 runs. It could be not lucky enough though
Sorry, something went wrong.
609dbb1
into
RustPython:main
Jan 15, 2026
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.