GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||
GeezerVison is showing github.com — gh-130474: Create and implement flaky resource by jtranq · Pull Request #130489 · python/cpython Conversation
|
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Some tests are not necessarily flaky. You should also update the command-line of libregretest python -m test --help
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Co-authored-by: Bénédikt Tran <[email protected]>
|
Oh, the docs are failing. I thought that we had documented it but no. My bad. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Co-authored-by: Bénédikt Tran <[email protected]>
There was an error while loading. Please reload this page.
Co-authored-by: Bénédikt Tran <[email protected]>
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Ok, so I'm not sure we should skip testSend for now because while it's marked as flaky, I've never seen it fail beforehand.
OTOH, test_stress_modifying_handlers is only flaky on free-threaded build so, if possible, we should not mark test_stress_modifying_handlers as flaky at all (testing on the regular would not be flaky at all!) Sorry for missing the point before but for my defense it's 1 AM here!
As for test_selflink, it's the only test that is really flaky actually and skipped (it's usually not flaky on an idle system, it's flaky on a stressed system). I would leave marking flaky tests in a separate PR (except for test_selflink).
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Co-authored-by: Bénédikt Tran <[email protected]>
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Co-authored-by: Bénédikt Tran <[email protected]>
There was an error while loading. Please reload this page.
Co-authored-by: Adam Turner <[email protected]>
|
Looks ok, but Victor is probably the best one to review changes to libregrtest. A |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Reading the linked issue in the comment for |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
It is though? at least according to my readings of #109959 (comment). Anyway, the thing is that it's still flaky as it randomly fails. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I dislike this change, If a test is known to be flaky, it should be either fixed or removed.
I suggest to remove test_selflink() in test_glob.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
I created #130551 to remove the flaky test. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I don't think that this "flaky" resource is a good idea.
I created #130551 to remove the flaky test.
I merged my PR.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
In light of #130474 (comment), I think it was a bad idea (my bad idea). At first, it seemed great but hiding a flaky test behind a decorator wouldn't help solving the problem, we could even forget about it! So I'll close the issue and this PR as the flaky tests I thought were flaky are being fixed (most of them happen on the free-threaded build and seem to be real issues, namely we should have written the tests differently). Thanks for the work though and sorry again! |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.