Builder curl-ares-solaris11-i386 Build #4265

Results:

Build successful

SourceStamp:

BuildSlave:

Reason:

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

Steps and Logfiles:

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

Build Properties:

Forced Build Properties:

Responsible Users:

1. Viktor Szakats

   commitohnoyoudont@vsz.me

Timing:

All Changes:

:

1. Change #251639

   Category	curl
   Changed by	Viktor Szakats <commitohnoyoudont@vsz.me>
   Changed at	Tue 09 Dec 2025 14:46:00
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	f450f3801b6b9dff0ea280f5fb4bf28203f7b313

   Comments

   GHA/windows: re-enable `taskkill`
   Nothing conclusive for the last ~30 days when `taskkill` was made
   a no-op. Jobs remained flaky with all known failure modes. Sometimes
   they finish green on the first run, sometimes they fail. Hard to say
   more without comparing detailed stats for this period and the
   preceding (or upcoming) one.
   
   In almost all runs, the PID to be killed did not exist at the time of
   check.
   
   Follow-up to 2701ac6a4d16a62130dad05be1c484903b8545c7 #19421
   Closes #19897

   Changed files

   • .github/workflows/windows.yml