Builder curl-threaded-solaris10-sparc Build #3838

Results:

Exception runtest mail result

SourceStamp:

BuildSlave:

Reason:

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

Steps and Logfiles:

1. git update ( 34 secs )
   1. stdio
2. Runtest './tests/testcurl.pl --nogitpull ...' failed ( 6 hrs, 54 mins, 54 secs )
   1. stdio
   2. resultlog
3. Mail result Mail result exception ( 0 secs )
   1. err.text
   2. err.html

Build Properties:

Forced Build Properties:

Responsible Users:

1. Viktor Szakats

   commitohnoyoudont@vsz.me
2. renovate[bot]

   29139614+renovate[bot]ohnoyoudont@users.noreply.github.com

Timing:

All Changes:

:

1. Change #285492

   Category	curl
   Changed by	Viktor Szakats <commitohnoyoudont@vsz.me>
   Changed at	Sun 11 Oct 2026 19:42:47
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	49f003f17391d547f7aea3e893308f169ede74ad

   Comments

   unit1664: add workaround for VS2019 16.3 - VS2022 17.4 x64 miscompile
   It affects `_MSC_VER >= 1923 && _MSC_VER <= 1934`, combined with `-O1`
   or `-O2`, and inlining reduced via `-Ob0` or `-Ob1` (CMake
   RelWithDebInfo config). Also with `-O2 -Ob2` (CMake Release config), in
   curl `units.exe` context.
   
   Introduced in: Visual Studio 2019 v16.3 (~2019-09-23)
   Fixed in: Visual Studio 2022 v17.5 (~2023-02-21)
   
   Godbolt reproducer: https://godbolt.org/z/T78GWxzeT
   
   As seen in AppVeyor CI:
   - CM VS2019, Debug  , x64, OpenSSL 3.0 + Schannel, Shared, !verbose, Build-tests: PASS
   - CM VS2019, Release, x64, OpenSSL 3.0 + Schannel, Shared, !verbose, Build-tests: FAIL test1664
   - CM VS2019, Release, x86, OpenSSL 3.0 + Schannel, Shared, !verbose, Build-tests: PASS
   - VS2017/VS2022, Debug/Release: PASS
   
   Fixing:
   ```
   # Visual Studio Community 2019 v16.11.50
   -- Building for: Visual Studio 16 2019
   -- Using CMake version 4.1.0
   -- Selecting Windows SDK version 10.0.26100.0 to target Windows 10.0.17763.
   -- The C compiler identification is MSVC 19.29.30159.0
   -- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64/cl.exe - skipped
   -- CMake platform flags: WIN32 MSVC-1929
   [...]
   -- Found _WIN32_WINNT=0x0a00
   -- Picky compiler options: -W4 -Wall -wd4061 -wd4191 -wd4255 -wd4464 -wd4548 -wd4574 -wd4668 -wd4710 -wd4711 -wd4746 -wd4820 -wd5045
   [...]
   test 1664 [unit tests for strparse.c string parsing functions]
   
      1664: stdout FAILED:
     --- log/check-expected
     +++ log/check-generated
     @@ -154,9 +154,9 @@
      3: (%62) 6, line 0[LF]
      4: (%5c) 6, line 0[LF]
      5: (%20) 6, line 0[LF]
     -6: (%0a) 0, line 1[LF]
     -7: (%0d) 0, line 1[LF]
     -8: (%0d) 0, line 1[LF]
     +6: (%00) 0, line 1[LF]
     +7: (%00) 0, line 1[LF]
     +8: (%0a) 0, line 1[LF]
      9: (%0c) 6, line 0[LF]
      10: (%00) 6, line 0[LF]
      curlx_str_hex[LF]
   [...]
   TESTFAIL: These test cases failed: 1664
   ```
   Ref: https://ci.appveyor.com/project/curlorg/curl/builds/54864988/job/m823tifoodo7tt1a
   
   Bug: https://github.com/curl/curl/pull/23306#issuecomment-6043152120
   Bug: https://github.com/curl/curl/pull/23306#issuecomment-6047833481
   Bug: https://github.com/curl/curl/pull/23306#issuecomment-6051687170
   Ref: https://github.com/curl/curl/pull/23347 (seeking a minimal reproducer)
   Cherry-picked from #23306
   
   Closes #23337

   Changed files

   • tests/unit/unit1664.c

2. Change #285497

   Category	curl
   Changed by	renovate[bot] <29139614+renovate[bot]ohnoyoudont@users.noreply.github.com>
   Changed at	Sun 11 Oct 2026 20:06:30
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	9b8e5442a65b935c08b97b1b9ddb9a82180e2f2c

   Comments

   GHA: update dependency pyspelling to v2.13
   Closes #23364

   Changed files

   • .github/scripts/requirements-docs.txt

3. Change #285501

   Category	curl
   Changed by	Viktor Szakats <commitohnoyoudont@vsz.me>
   Changed at	Sun 11 Oct 2026 20:07:12
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	e197647373e1e9210b60e81e84296633a802441c

   Comments

   test1664: delete duplicate sub-test
   Closes #23362

   Changed files

   • tests/data/test1664
   • tests/unit/unit1664.c

4. Change #285503

   Category	curl
   Changed by	Viktor Szakats <commitohnoyoudont@vsz.me>
   Changed at	Sun 11 Oct 2026 20:14:24
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	70c084a0123b468fe7078e3fc72c78e1b66394b6

   Comments

   docs: note CAINFO/SSL_VERIFYPEER/SSL_VERIFYSTATUS effect on LDAP
   Say how these TLS options behave when using mainline OpenLDAP, Apple's
   LDAP fork and WinLDAP.
   
   Also:
   - remove mention of `USE_OPENLDAP` internal C macro.
   - sync `CURLOPT_PINNEDPUBLICKEY` man page with the above.
     Follow-up to f2692b54f74b8bb6058ecd3cf4abcc96e8ab36ba #21682
   
   For reference about the two LDAP "tracks" curl supports:
   - lib/ldap.c: "legacy" LDAP, WinLDAP, Apple's OpenLDAP fork (existing
     releases reported as `OpenLDAP/2.4.28/Apple`, fixed version), IBMLDAP*,
     use their own TLS-backend, some curl TLS options explicitly supported
     build-time-macro/runtime-depending, `!USE_OPENLDAP`
     *: there is almost nothing publicly known about IBMLDAP.
   - lib/openssl.c: `USE_OPENLDAP`, mainline OpenLDAP, versioned, uses
     curl's TLS-backend, reports itself as `OpenLDAP/x.y.z`.
   
   Reported-by: Joshua Rogers
   
   Closes #23303

   Changed files

   • docs/libcurl/opts/CURLOPT_CAINFO.md
   • docs/libcurl/opts/CURLOPT_PINNEDPUBLICKEY.md
   • docs/libcurl/opts/CURLOPT_SSL_VERIFYPEER.md
   • docs/libcurl/opts/CURLOPT_SSL_VERIFYSTATUS.md