Builder curl-ares-solaris10-i386 Build #4598

Results:

Failed

SourceStamp:

BuildSlave:

Reason:

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

Steps and Logfiles:

1. git updating ( 16 secs )
   1. stdio
2. setproperty  
   1. - no logs -
3. setproperty_1  
   1. - no logs -
4. Runtest  
   1. - no logs -
5. Mail result  
   1. - no logs -

Build Properties:

Forced Build Properties:

Responsible Users:

1. Daniel Stenberg

   danielohnoyoudont@haxx.se
2. Viktor Szakats

   commitohnoyoudont@vsz.me

Timing:

All Changes:

:

1. Change #286165

   Category	curl
   Changed by	Daniel Stenberg <danielohnoyoudont@haxx.se>
   Changed at	Thu 15 Oct 2026 10:20:43
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	2f7edcd9ae5a671687aa87071870fc71a7d99d8b

   Comments

   tests: provide 'getrlimit' in curlinfo
   - Instead of having a custom rule in runtests.pl
   - make test 2380 depend on it
   
   Closes #23406

   Changed files

   • src/curlinfo.c
   • tests/data/test2380
   • tests/runtests.pl

2. Change #286166

   Category	curl
   Changed by	Viktor Szakats <commitohnoyoudont@vsz.me>
   Changed at	Thu 15 Oct 2026 10:32:27
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	bc229770522509126431c698dd4159108e3c5464

   Comments

   msvc: replace debug CRT GUI popups with stderr output
   When a curl binary is built with Visual Studio in debug mode, it uses
   the matching, debug-enabled CRT. The debug CRT by default pops up an
   interactive GUI dialog by default, also on CI machines, both on AppVeyor
   CI and GHA, on `assert()` and other low-level failures. This causes the
   CI job to appear hung, with nothing printed to the CI log, invisibly
   waiting for someone clicking on a GUI MessageBox. On a remote/headless
   CI machine this is unworkable. The job then quits on timeout, after
   blocking other queued tasks (for 1 hour on AppVeyor CI, 10-15 minutes in
   GHA/windows).
   
   To make such failures CI-friendly, fix by configuring this behavior in
   `curl.exe`, `servers.exe` and unit test binaries, to output all errors
   to stderr, and to `OutputDebugString()`, overiding the GUI popup.
   
   This can save a lot of hair-pulling.
   
   Example output, after this patch:
   ```
   Assertion failed: r == 10, file C:\projects\curl\tests\libtest\first.c, line 272
      abort() has been called
   ```
   
   Note, the default debug CRT behavior depends on a number of things, e.g.
   on a Server Core (or similar) Windows edition, or when run under a
   debugger. Assuming the default behavior is the expected one in most
   cases, this patch only reconfigures it for builds made in the curl CI.
   If you want to enable it, set the `CURL_CI` env to non-empty at
   configure time, or build with the `-DCURL_DEBUG_MSVC_CRTDBG` C macro.
   
   This issue does not apply to mingw-w64 builds, as tested with both UCRT
   and MSVCRT. They output the assert text to the CI logs out-of-the-box.
   
   Refs:
   https://learn.microsoft.com/cpp/c-runtime-library/reference/crtsetreportfile
   https://learn.microsoft.com/cpp/c-runtime-library/reference/crtsetreportmode
   https://learn.microsoft.com/cpp/c-runtime-library/reference/set-error-mode
   
   Ref: #23336
   Ref: edfa537100d6b5d2ac1b829c66757880afe59407 #16456
   Ref: https://github.com/curl/curl/discussions/14854
   Cherry-picked from #23306
   
   Closes #23400

   Changed files

   • CMakeLists.txt
   • lib/curl_setup.h
   • projects/Windows/generate.bat
   • src/tool_main.c
   • tests/libtest/first.c
   • tests/server/first.c