Builder curl-unthreaded-solaris11-i386 Build #5176

Results:

Build successful

SourceStamp:

BuildSlave:

Reason:

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

Steps and Logfiles:

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

Build Properties:

Forced Build Properties:

Responsible Users:

1. Stefan Eissing

   stefanohnoyoudont@eissing.org

Timing:

All Changes:

:

1. Change #269737

   Category	curl
   Changed by	Stefan Eissing <stefanohnoyoudont@eissing.org>
   Changed at	Sun 07 Jun 2026 14:39:10
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	fbcf10ab84d75e76029e50d0b22793a218181166

   Comments

   progress: fx CURLINFO time reporting
   Whack the times reported for a transfer (see
   https://curl.se/libcurl/c/curl_easy_getinfo.html#TIMES) into order for
   all variations of up-/download, http/ftp etc. Make sure they are
   reported in the documented order.
   
   There is still the *possibility* of PRETRANSFER being longer then
   POSTTRANSFER, if a server sends a response before an upload is done.
   POST is the time the first response byte is received, and PRE is the
   time the last byte was sent by curl.
   
   This may happen with more likelihood on HTTP/2 and 3 for a server
   rejected upload. But for successful uploads, the answer will almost over
   come afterwards.
   
   Undo the previous twists in lib500.c tests, adjust pytest timeline
   checks.
   
   Fixes #21828
   Reported-by: BazaarAcc32 on github
   Closes #21843

   Changed files

   • lib/multi.c
   • lib/progress.c
   • lib/progress.h
   • lib/request.c
   • lib/sendf.c
   • tests/http/testenv/curl.py
   • tests/libtest/lib500.c
   • tests/unit/unit1399.c