Builder curl-ares-solaris11-i386 Build #4571

Results:

Build successful

SourceStamp:

BuildSlave:

Reason:

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

Steps and Logfiles:

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

Build Properties:

Forced Build Properties:

Responsible Users:

1. Viktor Szakats

   commitohnoyoudont@vsz.me

Timing:

All Changes:

:

1. Change #256536

   Category	curl
   Changed by	Viktor Szakats <commitohnoyoudont@vsz.me>
   Changed at	Wed 28 Jan 2026 02:33:57
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	fb44e44d929f4e8eb140e5e1c7bd3a7f4d0e7d58

   Comments

   GHA/windows: fix shell, fix GHA fail to share cache between arm and intel Windows
   A cache entry created by windows-2022 is not picked up by
   windows-11-arm. Also a cache created by windows-11-arm is not picked up
   by windows-2022. Possibly related to this filed in 2025 June:
   https://github.com/actions/cache/issues/1622. Also tried
   `enableCrossOsArchive` to no avail. Unclear if these two runners count
   as distinct operating systems, I'd guess not. Cache entries are
   identical on the web UI. Via GH API they show up with the same cache key
   bot different "version" (hash) and different sizes, possibly due to the
   zstd vs. gzip bug above.
   
   Fixing (identical error text on either runner):
   ```
   Error: Failed to restore cache entry. Exiting as fail-on-cache-miss is set. Input key: Windows-stunnel-5.76-amd64
   ```
   
   Also fix a silly typo in the shell value.
   
   Follow-up to 0f54ca6150f5bff5e8eb8b165de86262e98f5e69 #20454
   Closes #20456

   Changed files

   • .github/workflows/windows.yml