Builder curl-ares-solaris11-i386 Build #4251

Results:

Build successful

SourceStamp:

BuildSlave:

Reason:

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

Steps and Logfiles:

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

Build Properties:

Forced Build Properties:

Responsible Users:

1. Viktor Szakats

   commitohnoyoudont@vsz.me

Timing:

All Changes:

:

1. Change #251383

   Category	curl
   Changed by	Viktor Szakats <commitohnoyoudont@vsz.me>
   Changed at	Mon 08 Dec 2025 13:08:14
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	7dd5bb77c397e7b7a7f323224c34488f1130399a

   Comments

   CI/windows: add torture tests with Schannel
   With Schannel and Unicode, `-shallow=13`. It finishes in 12 minutes,
   making it the slowest Windows job. It's still on par with torture jobs
   on other platforms (though they manage to fit `-shallow=25`).
   
   Also `-shallow=13` still caught leaks in multiple tests.
   
   Also:
   - test2300: exclude from CI Windows torture tests.
   - experimental.
   
   The downside of going with deeper torture tests, is that it requires
   increasing the job timeout. This in turns means that a hung job takes
   more minutes to be killed (due to GitHub bugs where a hung step does not
   honor the per-step timeout on Windows, another bug where a hung job gets
   killed +5 minutes above the workflow timeout, and another bug (or
   feature?) where other failed/hung jobs in the the workflow cannot be
   restarted till the last job finishes or gets killed. And all this
   probably related to a Perl bug which makes it hang on fork errors, which
   is turn related to Cygwin/MSYS2 runtime bugs which breaks fork in case
   of curl's mixed MSYS2-Perl/native-curl-binaries environment.)
   The end result in longer forced waits before being able to restart flaky
   jobs, which slows down iterations and annoying.
   
   Also tried:
   - non-c-ares job: detected known issues much less often.
   - replaced libidn2 with WinIDN: detected known issues much less often.
   - runtests -j9-j20 values: did not make a difference.
   - other `-shallow` values: 20 is the max feasible, but comes with the
     downside described above.
   
   Ref: #19675 (reboot of)
   Follow-up to f08417c4259a3b9a2e4d72a48fa02ce6502cb587 #19863
   
   Closes #19865

   Changed files

   • .github/workflows/windows.yml