Builder curl-ares-solaris10-sparc Build #3701
Results:
Build successful
SourceStamp:
| Project | curl |
| Repository | https://github.com/curl/curl.git |
| Branch | master |
| Revision | 69e8278149ce5e476bf4020b52e3928ec9dbf095 |
| Got Revision | 69e8278149ce5e476bf4020b52e3928ec9dbf095 |
| Changes | 1 change |
BuildSlave:
unstable10sReason:
The SingleBranchScheduler scheduler named 'schedule-curl-ares-solaris10-sparc' triggered this build
Steps and Logfiles:
Build Properties:
| Name | Value | Source |
|---|---|---|
| branch | master | Build |
| builddir | /export/home/buildbot-unstable10s/slave/curl-ares-solaris10-sparc | slave |
| buildername | curl-ares-solaris10-sparc | Builder |
| buildnumber | 3701 | Build |
| codebase | Build | |
| got_revision | 69e8278149ce5e476bf4020b52e3928ec9dbf095 | Git |
| osplatform | SPARC | SetPropertyFromCommand Step |
| osrelease | 10 | SetPropertyFromCommand Step |
| project | curl | Build |
| repository | https://github.com/curl/curl.git | Build |
| revision | 69e8278149ce5e476bf4020b52e3928ec9dbf095 | Build |
| scheduler | schedule-curl-ares-solaris10-sparc | Scheduler |
| slavename | unstable10s | BuildSlave |
| workdir | /export/home/buildbot-unstable10s/slave/curl-ares-solaris10-sparc | slave (deprecated) |
Forced Build Properties:
| Name | Label | Value |
|---|
Responsible Users:
- Viktor Szakatscommit@vsz.me
Timing:
| Start | Wed Aug 5 05:40:00 2026 |
| End | Wed Aug 5 20:16:52 2026 |
| Elapsed | 14 hrs, 36 mins, 51 secs |
All Changes:
:
Change #276978
Category curl Changed by Viktor Szakats <commit@vsz.me> Changed at Tue 04 Aug 2026 17:36:14 Repository https://github.com/curl/curl.git Project curl Branch master Revision 69e8278149ce5e476bf4020b52e3928ec9dbf095 Comments
servers: fix to reverse `SA_RESTART` option for `sigaction()` on modern codepath Historically servers used the deprecated `siginterrupt()` function to configure restart behavior on specific signals. It accepts a flag, where 1 means to remove the `SA_RESTART` option, and 0 means to enable it. In year 2021 3fb6e5a01001b8c7dfdc33a89041178aac381a27 introduced the modern alternative to the codebase, replacing `siginterrupt()` with `sigaction()`. After this patch, supporting, modern, systems reacted on the same flag, but, by accident, set the `SA_RESTART` bit when flag is 1, and did not set it when 0. This reversed the previous behavior, and the one still used on the `siginterrupt()` legacy codepath. Fix it by revesring the `SA_RESTART` logic for the `sigaction()` codepath, syncing it with the pre-existing behavior. I find it odd this did not cause any perceivable issue for 5 years, even though it's the active one in most Unix envs. Spotted by GitHub Code Quality, though suggesting to fix `siginterrupt()` calls. But looking into the history, those were correct all along. Refs: https://pubs.opengroup.org/onlinepubs/9699919799/functions/siginterrupt.html https://pubs.opengroup.org/onlinepubs/9699919799/functions/sigaction.html https://www.man7.org/linux/man-pages/man3/siginterrupt.3.html https://www.man7.org/linux/man-pages/man2/sigaction.2.html Follow-up to 3fb6e5a01001b8c7dfdc33a89041178aac381a27 #6529 Closes #22037
Changed files
- tests/server/util.c