Builder curl-threaded-solaris10-sparc Build #3402

Results:

Build successful

SourceStamp:

BuildSlave:

Reason:

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

Steps and Logfiles:

1. git update ( 10 secs )
   1. stdio
2. Runtest './tests/testcurl.pl --nogitpull ...' ( 15 mins, 38 secs )
   1. stdio
   2. resultlog
3. Mail result 'cat resultlog ...' ( 10 secs )
   1. stdio

Build Properties:

Forced Build Properties:

Responsible Users:

1. Stefan Eissing

   stefanohnoyoudont@eissing.org
2. Viktor Szakats

   commitohnoyoudont@vsz.me

Timing:

All Changes:

:

1. Change #253989

   Category	curl
   Changed by	Stefan Eissing <stefanohnoyoudont@eissing.org>
   Changed at	Sat 03 Jan 2026 00:48:54
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	ac06643f7166b7a131643b4784b818a0bbf044c6

   Comments

   pytest: test 03_02 stabilize (curl_ngtcp2)
   The special handling for draining server connections during a connect
   attempt was only done on CURLE_RECV_ERROR. But it may also happen when
   ngtcp2 errors on writing data. Check for CURLE_SEND_ERROR also.
   
   Ref: #20112
   Closes #20162

   Changed files

   • lib/vquic/curl_ngtcp2.c

2. Change #253990

   Category	curl
   Changed by	Stefan Eissing <stefanohnoyoudont@eissing.org>
   Changed at	Sat 03 Jan 2026 00:48:54
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	2c32ab12a01d24fa2d0b9db77999379a87d4ee61

   Comments

   pytest: test 07_70 stabilize (curl_ngtcp2)
   We recently allowed a larger send buffer in ngtcp2 streams. This allowed
   curl to send more early data then previously when the server was slow in
   performing the handshake. This led to flaky test failures when the
   amount of early data was larger than expected.
   
   Change test expectations to allow for varying amount of early data.
   
   Ref: #20112
   Closes #20161

   Changed files

   • lib/vquic/curl_ngtcp2.c
   • tests/http/test_07_upload.py

3. Change #253991

   Category	curl
   Changed by	Stefan Eissing <stefanohnoyoudont@eissing.org>
   Changed at	Sat 03 Jan 2026 00:48:54
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	a348f19bd158197a3932b5c783edc2fb03abda2c

   Comments

   pytest: test 07_22 stabilize
   Do not generate a 400 response code, but use a 200 one. The upload needs
   to fail on sending, not on seeing a 400 response. Seeing a 400 before
   the sending fails (when CI timings shift) will expose the wrong error
   code.
   
   Ref: #20112
   Closes #20164

   Changed files

   • tests/http/test_07_upload.py

4. Change #253993

   Category	curl
   Changed by	Viktor Szakats <commitohnoyoudont@vsz.me>
   Changed at	Sat 03 Jan 2026 01:02:41
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	d07024cf9375a57ca737a97c24dbfc7e7083e1bb

   Comments

   GHA: restore `--shallow` value for some torture tests
   It also means that now all torture test-pairs use the same shallowness,
   while earlier FTP used 20.
   
   Also:
   - This made macOS torture jobs slow enough to split them into 3 jobs.
   
   Follow-up to 2cbcde90e7a5eb7144079dcacc21393322b1daf7 #20153
   
   Closes #20172

   Changed files

   • .github/workflows/linux.yml
   • .github/workflows/macos.yml