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

Builder curl-threaded-solaris11-i386 Build #3869

Results:

Build successful

SourceStamp:

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

BuildSlave:

unstable11x

Reason:

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

Steps and Logfiles:

  1. git update ( 14 secs )
    1. stdio
  2. Runtest './tests/testcurl.pl --nogitpull ...' ( 52 mins, 31 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-i386 slave
buildername curl-threaded-solaris11-i386 Builder
buildnumber 3869 Build
codebase Build
got_revision b6a5f672597a06bdf4361a2e70bb53c6f097105f Git
osplatform I386 SetPropertyFromCommand Step
osrelease 11 SetPropertyFromCommand Step
project curl Build
repository https://github.com/curl/curl.git Build
revision b6a5f672597a06bdf4361a2e70bb53c6f097105f Build
scheduler schedule-curl-threaded-solaris11-i386 Scheduler
slavename unstable11x BuildSlave
workdir /export/home/buildbot/slave/curl-threaded-solaris11-i386 slave (deprecated)

Forced Build Properties:

NameLabelValue

Responsible Users:

  1. Jay Satiro

Timing:

StartFri Aug 22 08:02:43 2025
EndFri Aug 22 09:58:59 2025
Elapsed1 hrs, 56 mins, 16 secs

All Changes:

:

  1. Change #243509

    Category curl
    Changed by Jay Satiro <raysatiroohnoyoudont@yahoo.com>
    Changed at Fri 22 Aug 2025 07:50:28
    Repository https://github.com/curl/curl.git
    Project curl
    Branch master
    Revision b6a5f672597a06bdf4361a2e70bb53c6f097105f

    Comments

    schannel: improve handshake procedure
    - During handshake, do not require reading more data if unprocessed
      encrypted data that may be a complete TLS record is already available.
    
    - During handshake, check that the socket is writeable before processing
      encrypted data that may require an immediate reply to the server.
    
    These two fixes are for issues that were found during renegotiation
    testing but could affect any handshake.
    
    Prior to this change it was possible in some abnormal network conditions
    for the Schannel TLS handshake procedure to erroneously wait or error.
    
    Ref: https://github.com/curl/curl/pull/18125
    
    Closes https://github.com/curl/curl/pull/18323

    Changed files

    • lib/vtls/schannel.c