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

Builder curl-threaded-solaris11-sparc Build #5631

Results:

Build successful

SourceStamp:

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

BuildSlave:

unstable11s

Reason:

The SingleBranchScheduler scheduler named 'schedule-curl-threaded-solaris11-sparc' triggered this build

Steps and Logfiles:

  1. git update ( 6 secs )
    1. stdio
  2. Runtest './tests/testcurl.pl --nogitpull ...' ( 23 mins, 17 secs )
    1. stdio
    2. resultlog
  3. Mail result 'cat resultlog ...' ( 0 secs )
    1. stdio

Build Properties:

NameValueSource
branch master Build
builddir /export/home/buildbot/slave/curl-threaded-solaris11-sparc slave
buildername curl-threaded-solaris11-sparc Builder
buildnumber 5631 Build
codebase Build
got_revision 567803db797ae656dbdf4a630785e51b68798060 Git
osplatform SPARC SetPropertyFromCommand Step
osrelease 11 SetPropertyFromCommand Step
project curl Build
repository https://github.com/curl/curl.git Build
revision 567803db797ae656dbdf4a630785e51b68798060 Build
scheduler schedule-curl-threaded-solaris11-sparc Scheduler
slavename unstable11s BuildSlave
workdir /export/home/buildbot/slave/curl-threaded-solaris11-sparc slave (deprecated)

Forced Build Properties:

NameLabelValue

Responsible Users:

  1. Stefan Eissing

Timing:

StartWed Apr 8 23:25:02 2026
EndThu Apr 9 00:11:44 2026
Elapsed46 mins, 42 secs

All Changes:

:

  1. Change #264031

    Category curl
    Changed by Stefan Eissing <stefanohnoyoudont@eissing.org>
    Changed at Wed 08 Apr 2026 23:15:39
    Repository https://github.com/curl/curl.git
    Project curl
    Branch master
    Revision 567803db797ae656dbdf4a630785e51b68798060

    Comments

    dns: https-eyeballing async
    Make cf-https-connect work async correctly:
    - only start first baller when at least one A/AAAA address
      is available
    - select first connect attempt after that with HTTPS-RR info
      there or not.
    - select second connect attempt only when HTTPS-RR is resolved
      (may have resolved to "not known") and select possible ALPN
      from things known by then. May not select any second attempt
      when first already covers everything.
    
    This means when the HTTPS-RR is known at/before the first address
    is resolved, everything behaves as before. When the HTTPS-RR is
    late, a first connection attempt will have been started. Any
    ALPN preference from the HTTPS-RR that is not already ongoing will
    then start the second attempt.
    
    For HTTPS-RRs that recommend 2 or more ALPNs, the first will always
    be attempted: either it is already ongong or it will be the ALPN
    for the second attempt. The 2nd ALPN recommendation from HTTPS-RR
    *may* be honored or not, depending on what is already selected.
    
    The difference in behaviour between early/late HTTPS-RR resolve
    cannot be helped - unless we do not perform any attempts before
    it arrives. Trade offs.
    
    Closes #21267

    Changed files

    • lib/cf-dns.c
    • lib/cf-dns.h
    • lib/cf-https-connect.c
    • lib/vquic/vquic.c