Builder curl-threaded-solaris10-sparc Build #2992

Results:

Failed runtest

SourceStamp:

BuildSlave:

Reason:

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

Steps and Logfiles:

1. git update ( 1 mins, 0 secs )
   1. stdio
2. Runtest './tests/testcurl.pl --nogitpull ...' failed ( 5 hrs, 33 mins, 45 secs )
   1. stdio
   2. resultlog
3. Mail result 'cat resultlog ...' ( 9 secs )
   1. stdio

Build Properties:

Forced Build Properties:

Responsible Users:

1. Stefan Eissing

   stefanohnoyoudont@eissing.org

Timing:

All Changes:

:

1. Change #244497

   Category	curl
   Changed by	Stefan Eissing <stefanohnoyoudont@eissing.org>
   Changed at	Fri 05 Sep 2025 13:17:39
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	0b091328773c64e23f5c4739da74527093c6a5ab

   Comments

   websocket: handling of PONG frames
   The auto PONG frames were inserted into the connection at the time
   a PING had been decoded, irregardless if an upstream frame was just
   in the middle of being assembled.
   
   Add PONG frames only to the buffer if there is no frame currently
   assemebled and, if it is, set the control frame aside. This control
   frame is then added on the first opportunity of a "clean" send buffer.
   
   There is only a single control frame set aside at a time. This means
   a double PING will, when the PONG cannot be sent right away, only
   send the last PONG.
   
   I imagine this is fine. We want to prevent the endless buffering of
   PONG frames on a connection where the server sends but does no receives.
   
   Reported-by: Calvin Ruocco
   Fixes #16706
   Closes #18479

   Changed files

   • lib/ws.c