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-83714: Check for struct statx.stx_atomic_write_unit_max_opt in configure by jbosboom · Pull Request #140185 · python/cpython Conversation
|
|
!buildbot AMD64 CentOS9 NoGIL 3.x |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
You don't have write permissions to trigger a build |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
#139178 failed on the AMD64 CentOS9 NoGIL 3.x (tier-1), ARM64 Raspbian Debug 3.x (tier-3) and ARM Raspbian 3.x (tier-3) buildbots. I need someone with the appropriate permissions to run those before merging. This should be skip-news. |
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.
This seems like a reasonable approach to me; a core dev can trigger the bots to validate (although the queue can take a while to get to the top of).
I think skip news works as this is falls under "If a change is a fix (or other adjustment) to an earlier unreleased change and the original NEWS entry remains valid, then no additional entry is needed."
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
!buildbot AMD64.CentOS9.NoGIL |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
🤖 New build scheduled with the buildbot fleet by @encukou for commit 37ebb56 🤖 Results will be shown at: https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F140185%2Fmerge The command will test the builders whose names match following regular expression: The builders matched are:
|
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.
LGTM, but let me check on buildbots.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
!buildbot Raspbian |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
🤖 New build scheduled with the buildbot fleet by @vstinner for commit 37ebb56 🤖 Results will be shown at: https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F140185%2Fmerge The command will test the builders whose names match following regular expression: The builders matched are:
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Buildbot issues to expect:
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Buildbots passed successfully:
Alright, AMD64 CentOS9 NoGIL Refleaks PR failed on an unrelated test: |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
Merged, thanks @jbosboom. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
…in configure (python#140185) stx_atomic_write_unit_max_opt was added in Linux 6.16, but is controlled by the STATX_WRITE_ATOMIC mask bit added in Linux 6.11. That's safe at runtime because all kernels clear the reserved space in struct statx and zero is a valid value for stx_atomic_write_unit_max_opt, and it avoids allocating another mask bit, which are a limited resource. But it also means the kernel headers don't provide a way to check whether stx_atomic_write_unit_max_opt exists, so add a configure check.
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.