Builder curl-threaded-solaris10-i386 Build #3502

Results:

Failed runtest

SourceStamp:

BuildSlave:

Reason:

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

Steps and Logfiles:

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

Build Properties:

Forced Build Properties:

Responsible Users:

1. Yedaya Katsman

   yedaya.kaohnoyoudont@gmail.com

Timing:

All Changes:

:

1. Change #231841

   Category	curl
   Changed by	Yedaya Katsman <yedaya.kaohnoyoudont@gmail.com>
   Changed at	Tue 10 Jun 2025 15:46:13
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	bc7d88cc8af57db233b5a48c57bcd3b383591779

   Comments

   tests: torture: don't duplicate valgrind command
   When running torture tests with valgrind enabled, the torture function
   got a command line that already had the valgrind invocation in it. It
   added another, at the end resulting in an empty valgrind log file.
   
   Remove the duplicate logic adding valgrind, which already had a bit of
   different logic that wasn't updated when the other one was.
   
   Closes #17501

   Changed files

   • tests/runner.pm

2. Change #231842

   Category	curl
   Changed by	Yedaya Katsman <yedaya.kaohnoyoudont@gmail.com>
   Changed at	Tue 10 Jun 2025 15:46:47
   Repository	https://github.com/curl/curl.git
   Project	curl
   Branch	master
   Revision	05ffeeda0c8f6718f979ea5c7fe06ab20b42a5f4

   Comments

   tests: fail torture if !valgrind&threaded resolver
   We don't check the memory debug output with the threaded resolver, so
   the only way to do it with with valgrind.
   
   Also move the disabling of memory tracking to where we log that we're
   doing it.
   
   Closes #17501

   Changed files

   • tests/runtests.pl