Builder curl-ares-solaris11-i386 Build #3560

Results:

Build successful

SourceStamp:

BuildSlave:

Reason:

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

Steps and Logfiles:

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

Build Properties:

Forced Build Properties:

Responsible Users:

1. Daniel Stenberg

   danielohnoyoudont@haxx.se
2. Ruocco, Calvin

   calvin.ruoccoohnoyoudont@vector.com
3. Stefan Eissing

   stefanohnoyoudont@eissing.org

Timing:

All Changes:

:

1. Change #231220

   Category	curl
   Changed by	Stefan Eissing <stefanohnoyoudont@eissing.org>
   Changed at	Mon 02 Jun 2025 11:02:14
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	e61c287e73cb07f83396db3048f3bb3b2f3068e4

   Comments

   test1510: fix expectation
   The test had `Closing connection 0` in its expectations, but a stripfile
   expression that removes such lines. No recent changes, but started failing
   this morning.
   
   Too little coffee for me? Or what triggered this?
   
   Closes #17515

   Changed files

   • tests/data/test1510

2. Change #231221

   Category	curl
   Changed by	Stefan Eissing <stefanohnoyoudont@eissing.org>
   Changed at	Mon 02 Jun 2025 11:03:10
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	04c3895ceb2dbf9e62850080a658f9f26ad2293e

   Comments

   tests: improve server start reliability
   Fix all lookups of the port a server is using by
   - unlinking the portfile before the start
   - waiting `timeout` seconds for the port file to exist
     and contain a positive number
   - check results and fail server start when port could
     not be determined
   
   Closes #17516

   Changed files

   • tests/processhelp.pm
   • tests/servers.pm

3. Change #231224

   Category	curl
   Changed by	Ruocco, Calvin <calvin.ruoccoohnoyoudont@vector.com>
   Changed at	Mon 02 Jun 2025 11:15:38
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	d3594be6531df3d5eafcdd09f84ad9dee1777028

   Comments

   ws: tests and fixes
   This started out as regression tests for the `curl_ws_recv()` and
   `curl_ws_send()` implementation and ended up with a bugfix, additional
   protocol validation and minor logging improvements.
   
   - Fix reset of fragmented message decoder state when a PING/PONG is
     received in between message fragments.
   
   - Fix undefined behavior (applying zero offset to null pointer) in
     curl_ws_send() when the given buffer is NULL.
   
   - Detect invalid overlong PING/PONG/CLOSE frames.
   - Detect invalid fragmented PING/PONG/CLOSE frames.
   - Detect invalid sequences of fragmented frames.
   
     - a) A continuation frame (0x80...) is received without any ongoing
       fragmented message.
     - b) A new fragmented message is started (0x81/0x01/0x82/0x02...)
       before the ongoing fragmented message has terminated.
   
   - Made logs for invalid opcodes easier to understand.
   - Moved noisy logs to the `CURL_TRC_WS` log level.
   - Unified the prefixes for WebSocket log messages: `[WS] ...`
   
   - Add env var `CURL_WS_FORCE_ZERO_MASK` in debug builds.
   
     - If set, it forces the bit mask applied to outgoing payloads to
       0x00000000, which effectively means the payload is not masked at
       all. This drastically simplifies defining the expected `<protocol>`
       data in test cases.
   
   - 2700: Frame types
   - 2701: Invalid opcode 0x3
   - 2702: Invalid opcode 0xB
   - 2703: Invalid reserved bit RSV1 _(replaces 2310)_
   - 2704: Invalid reserved bit RSV2
   - 2705: Invalid reserved bit RSV3
   - 2706: Invalid masked server message
   - 2707: Peculiar frame sizes _(part. replaces 2311)_
   - 2708: Automatic PONG
   - 2709: No automatic PONG _(replaces 2312)_
   - 2710: Unsolicited PONG
   - 2711: Empty PING/PONG/CLOSE
   - 2712: Max sized PING/PONG/CLOSE
   - 2713: Invalid oversized PING _(replaces 2307)_
   - 2714: Invalid oversized PONG
   - 2715: Invalid oversized CLOSE
   - 2716: Invalid fragmented PING
   - 2717: Invalid fragmented PONG
   - 2718: Invalid fragmented CLOSE
   - 2719: Fragmented messages _(part. replaces 2311)_
   - 2720: Fragmented messages with empty fragments
   - 2721: Fragmented messages with interleaved pong
   - 2722: Invalid fragmented message without initial frame
   - 2723: Invalid fragmented message without final frame
   
   - 2305: curl_ws_recv() loop reading three larger frames
     - This test involuntarily sent an invalid sequence of opcodes (0x01...,0x01...,0x81...) , but neither libcurl nor the test caught this! The correct sequence was tested in 2311 (0x01...,0x00...,0x80...). See below for 2311.
     - Validation of the opcode sequence was added to libcurl and is now tested in 2723.
     - Superseded by 2719 (fragmented message) and 2707 (large frames).
   - 2307: overlong PING payload
     - The tested PING payload length check was actually missing, but the test didn't catch this since it involuntarily sent an invalid opcode (0x19... instead of 0x89...) so that the expected error occurred, but for the wrong reason.
     - Superseded by 2713.
   - 2310: unknown reserved bit set in frame header
     - Superseded by 2703 and extended by 2704 and 2705.
   - 2311: curl_ws_recv() read fragmented message
     - Superseded by 2719 (fragmented message) and 2707 (large frames).
   - 2312: WebSockets no auto ping
     - Superseded by 2709.
   
   - No tests for `CURLOPT_WRITEFUNCTION`.
   - No tests for sending of invalid frames/fragments.
   
   Closes #17136

   Changed files

   • .mailmap
   • docs/libcurl/libcurl-env-dbg.md
   • lib/ws.c
   • tests/data/Makefile.am
   • tests/data/test2304
   • tests/data/test2305
   • tests/data/test2307
   • tests/data/test2310
   • tests/data/test2311
   • tests/data/test2312
   • tests/data/test2700
   • tests/data/test2701
   • tests/data/test2702
   • tests/data/test2703
   • tests/data/test2704
   • tests/data/test2705
   • tests/data/test2706
   • tests/data/test2707
   • tests/data/test2708
   • tests/data/test2709
   • tests/data/test2710
   • tests/data/test2711
   • tests/data/test2712
   • tests/data/test2713
   • tests/data/test2714
   • tests/data/test2715
   • tests/data/test2716
   • tests/data/test2717
   • tests/data/test2718
   • tests/data/test2719
   • tests/data/test2720
   • tests/data/test2721
   • tests/data/test2722
   • tests/data/test2723
   • tests/http/test_20_websockets.py
   • tests/libtest/Makefile.inc
   • tests/libtest/lib2305.c
   • tests/libtest/lib2310.c
   • tests/libtest/lib2311.c
   • tests/libtest/lib2312.c
   • tests/libtest/lib2700.c

4. Change #231225

   Category	curl
   Changed by	Daniel Stenberg <danielohnoyoudont@haxx.se>
   Changed at	Mon 02 Jun 2025 11:19:04
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	d591bc141629d13170e704785609e8482e814f94

   Comments

   tool_getparam: make --no-anyauth not be accepted
   It was previously just ignored, now it triggers an error. It was never
   documented (nor intended) to work.
   
   Fixes #17508
   Reported-by: Dan Fandrich
   Closes #17511

   Changed files

   • src/tool_getparam.c