Builder curl-ares-solaris11-sparc Build #6029

Results:

Build successful

SourceStamp:

BuildSlave:

Reason:

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

Steps and Logfiles:

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

Build Properties:

Forced Build Properties:

Responsible Users:

1. Viktor Szakats

   commitohnoyoudont@vsz.me

Timing:

All Changes:

:

1. Change #270733

   Category	curl
   Changed by	Viktor Szakats <commitohnoyoudont@vsz.me>
   Changed at	Fri 12 Jun 2026 23:27:23
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	879a1514c3cf41926fd565db9e9ae62ab9733554

   Comments

   socket: introduce `SOCK_EAGAIN()` and use it
   To contain the logic of checking for both `EWOULDBLOCK` and/or `EAGAIN`
   depending on platform/availability. Also to avoid checking for both if
   they mapp to the same value, and to avoid PP guards around use.
   
   This also ensures `EAGAIN` is consistently not checked on Windows, where
   headers defined it, but `SOCKERRNO` never returns it, because curl maps
   it to `WSAGetLastError()`.
   
   If they map to the same value, checking them both in an `if` expression
   trips GCC warning `-Wlogical-op` (the same way it triggers duplicate
   case value error in `switch`).
   
   Also:
   - replace two `switch()` statements with the new macro.
   - tests/server/sws: make two outliers use the new macro that were only
     checking for `EWOULDBLOCK` before this patch, in `connect_to()`.
   - move variables to the left-side of expressions, where missing.
   - rustls: use a variant of this macro that uses raw `EWOULDBLOCK`.
     Tried tracing it back to the origins, but I couldn't figure out if
     this is working as expected on all supported Windows versions in
     Rust. It seems to be using `GetLastError()`, according to
     https://docs.rs/system_error/0.2.0/system_error/, which would be
     probably incorrect.
   
   Notes:
   - it's probably a good idea to assign `SOCKERRNO` to a variable before
     passing it to this macro.
   
   Cherry-picked from #21893
   
   Closes #21992

   Changed files

   • lib/cf-socket.c
   • lib/curl_setup.h
   • lib/socketpair.c
   • lib/vquic/vquic.c
   • lib/vtls/rustls.c
   • src/tool_cb_rea.c
   • tests/server/sws.c