Builder curl-threaded-solaris10-i386 Build #4596

Results:

Failed runtest

SourceStamp:

BuildSlave:

Reason:

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

Steps and Logfiles:

1. git update ( 9 secs )
   1. stdio
2. Runtest './tests/testcurl.pl --nogitpull ...' failed ( 4 hrs, 47 mins, 17 secs )
   1. stdio
   2. resultlog
3. Mail result 'cat resultlog ...' ( 1 secs )
   1. stdio

Build Properties:

Forced Build Properties:

Responsible Users:

1. Daniel Stenberg

   danielohnoyoudont@haxx.se
2. Viktor Szakats

   commitohnoyoudont@vsz.me

Timing:

All Changes:

:

1. Change #285215

   Category	curl
   Changed by	Daniel Stenberg <danielohnoyoudont@haxx.se>
   Changed at	Fri 09 Oct 2026 16:10:05
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	686ec81f251e01ba45eff1f2e3fbb5c387b11e88

   Comments

   http_chunks: accept exactly 17 characters chunk-size
   On all systems, not just 64-bit: clarify the comment.
   
   Ref: #23333
   Closes #23334

   Changed files

   • lib/http_chunks.h

2. Change #285217

   Category	curl
   Changed by	Viktor Szakats <commitohnoyoudont@vsz.me>
   Changed at	Fri 09 Oct 2026 16:31:25
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	d3e7cafc06f425b6a6ad0989867bb2a8e8afbd9f

   Comments

   GHA/windows: drop unused `-ac` runtests options
   The external curl copy passed as its argument is used to access CI APIs.
   It's a no-op outside AppVeyor CI and Azure CI.
   
   Cherry-picked from #23306
   
   Closes #23335

   Changed files

   • .github/workflows/windows.yml

3. Change #285235

   Category	curl
   Changed by	Viktor Szakats <commitohnoyoudont@vsz.me>
   Changed at	Fri 09 Oct 2026 19:34:57
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	098d3a0d4044d8a3f0a8617a5a5a30cde90fba26

   Comments

   runtests: unset `CURL_MEMDEBUG` for curl requests made to the CI API
   runtests has an automatic feature which detects AppVeyor and Azure CI,
   and communicates runtests test progress and results through the CI API.
   This feature uses the curl tool to send the API requests. It offers the
   `-ac` TFLAGS option to configure an external curl tool for these
   requests, otherwise it uses the freshly built curl tool.
   
   This curl is invoked from the same environment used to invoke the actual
   test curl commands and unit test binaries, thus it has `CURL_MEMDEBUG`
   set and pointing to a test-specific log file.
   
   The issue arises when the curl tool making the API request happens to be
   a debug-enabled one, with the 'TrackMemory' feature enabled. Such curl
   picks up the `CURL_MEMDEBUG` env and dumps it's own, memory tracing
   output into the test's log file. This causes flaky but consistent test
   failures, with bizarre errors, reporting corrupt or unsupported lines,
   and/or just not matching the expected output.
   
   When relying on the freshly built curl (without the `-ac` option) this
   is guaranteed to happen for all debug-enabled builds. As I found out the
   hard way, AppVeyer CI Windows 2012/2016 machines come preinstalled with
   an MSYS2 curl, which has _TrackMemory enabled_, which was explicitly set
   to fix this issue, and caused the very same problem.
   
   To fix, ensure to unset `CURL_MEMDEBUG` before making the API request
   with curl, avoiding this issue with all curl builds. It fixes future
   suprises, and also makes the freshly built curl a viable option in most
   cases, even in debug-enabled builds. (the requirement is to have
   working, cleartext HTTP support; for the AppVeyor API.)
   
   Example fails:
   ```
   ** MEMORY FAILURE
   Not recognized prefix line: SEND sendf.c:391 send(424) = 424
   Not recognized prefix line: RECV sendf.c:459 recv(102400) = 114
    3216: memory FAILED
   [...]
   test 3306 [thrdqueue retries failed thread starts on receive]
   
   ** MEMORY FAILURE
   Not recognized prefix line: il))
   [...]
   test 1607 [CURLOPT_RESOLVE parsing]
   
   ** MEMORY FAILURE
   Not recognized prefix line: 47 calloc(2,8) = 0xde7a13368
   CUSTOMBUILD : FREE error : No memory allocated: MEM C:/projects/curl/lib/url.c:303 free(0xde7a145b8)
   CUSTOMBUILD : FREE error : No memory allocated: MEM C:/projects/curl/lib/url.c:3
   ```
   Notice, current curl no longer emits SEND/RECV log events. The line
   numbers match the source code of curl 7.65.3. The other two examples
   are foreign / corrupt log lines.
   
   The TrackMemory-enabled curl was shipping in MSYS2, and come
   preinstalled on these AppVeyor CI machine, as
   `C:\msys64\usr\bin\curl.exe`:
   - Visual Studio 2015 (Windows Server 2012 R2)
   - Visual Studio 2017 (Windows 2016)
   
   ```
   curl 7.65.3 (x86_64-pc-msys) libcurl/7.65.3 OpenSSL/1.1.1c zlib/1.2.11 brotli/1.0.7 libidn2/2.2.0 libpsl/0.21.0 (+libidn2/2.2.0) libssh2/1.8.2 nghttp2/1.39.1
   Release-Date: 2019-07-19
   Protocols: dict file ftp ftps gopher http https imap imaps pop3 pop3s rtsp scp sftp smb smbs smtp smtps telnet tftp.
   Features: AsynchDNS brotli Debug GSS-API HTTP2 HTTPS-proxy IDN IPv6 Kerberos Largefile libz Metalink NTLM NTLM_WB PSL SPNEGO SSL TLS-SRP TrackMemory UnixSockets
   ```
   
   Bug: https://github.com/curl/curl/pull/23306#issuecomment-6043152120
   Bug: https://github.com/curl/curl/pull/23306#issuecomment-6048388544
   Bug: https://github.com/curl/curl/pull/23306#issuecomment-6048790733
   Bug: https://github.com/curl/curl/pull/23306#issuecomment-6079755601
   Cherry-picked from #23306
   
   Closes #23332

   Changed files

   • tests/appveyor.pm
   • tests/azure.pm