-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
test_os.TimerfdTests is flaky #126112
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
I think this bug is similar to #124873 , though that one was on Android, while this one is on a (heavily-customized) Gentoo Linux. |
Update: Upgrading to 3.13.1 still resulted in a similar error:
|
Interesting – I couldn't see how the test could fail this way unless the process had been suspended for 1/8 of a second. This seemed unlikely even on an Android emulator, but possible given Android's customized process scheduler. But if it's failing even on Linux, there's probably some other cause. |
We've seen this in the Yocto Project when running the python tests inside a qemu on a heavily loaded system: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15743. |
The Yocto failure isn't in the same test, it's in a different timerfd test which is much more timing-sensitive. See discussion in #130508. |
I notice that most of the timerfd tests create an FD and never close it. This shouldn't directly lead to the failure above, because every test uses a separate FD, but it would still be worth cleaning up. |
FTR, it also failed on AMD Debian: #129797 (comment) |
I saw this locally on Ubuntu 22.04 x86-64:
|
@colesbury It also fails on NetBSD, see #131266 |
test_time fails randomly on s390x Fedora Stable LTO + PGO 3.x. Example: https://buildbot.python.org/#/builders/1627/builds/314
|
Bug report
Bug description:
When compiling
dev-lang/python-3.13.0
on Gentoo, the following tests failed:USE
flags used are:which resulted in the following
./configure
invocation:CPython versions tested on:
3.13.0, 3.13.1
Operating systems tested on:
Linux (Gentoo)
The text was updated successfully, but these errors were encountered: