Home - Waterfall Grid T-Grid Console Builders Recent Builds Buildslaves Changesources - JSON API - About

Builder curl-unthreaded-solaris10-sparc Build #14066

Results:

Failed runtest

SourceStamp:

Projectcurl
Repositoryhttps://github.com/curl/curl.git
Branchmaster
Revision69e8278149ce5e476bf4020b52e3928ec9dbf095
Got Revision69e8278149ce5e476bf4020b52e3928ec9dbf095
Changes1 change

BuildSlave:

unstable10s

Reason:

The SingleBranchScheduler scheduler named 'schedule-curl-unthreaded-solaris10-sparc' triggered this build

Steps and Logfiles:

  1. git update ( 15 secs )
    1. stdio
  2. Runtest './tests/testcurl.pl --nogitpull ...' failed ( 6 hrs, 46 mins, 44 secs )
    1. stdio
    2. resultlog
  3. Mail result 'cat resultlog ...' ( 0 secs )
    1. stdio

Build Properties:

NameValueSource
branch master Build
builddir /export/home/buildbot-unstable10s/slave/curl-unthreaded-solaris10-sparc slave
buildername curl-unthreaded-solaris10-sparc Builder
buildnumber 14066 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-unthreaded-solaris10-sparc Scheduler
slavename unstable10s BuildSlave
workdir /export/home/buildbot-unstable10s/slave/curl-unthreaded-solaris10-sparc slave (deprecated)

Forced Build Properties:

NameLabelValue

Responsible Users:

  1. Viktor Szakats

Timing:

StartWed Aug 5 05:08:43 2026
EndWed Aug 5 19:55:57 2026
Elapsed14 hrs, 47 mins, 13 secs

All Changes:

:

  1. Change #276978

    Category curl
    Changed by Viktor Szakats <commitohnoyoudont@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