Builder wget-solaris10-i386 Build #449

Results:

Failed shell shell_1 shell_2 shell_3

SourceStamp:

BuildSlave:

Reason:

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

Steps and Logfiles:

1. git update ( 1 secs )
   1. stdio
2. shell 'bash bootstrap' failed ( 1 secs )
   1. stdio
3. shell_1 './configure' failed ( 0 secs )
   1. stdio
   2. src/config.h
   3. config.log
4. shell_2 'gmake' failed ( 0 secs )
   1. stdio
5. shell_3 'gmake check' failed ( 0 secs )
   1. stdio
   2. tests-unit-tests.log
   3. tests-test-suite.log
   4. testenv-test-suite.log

Build Properties:

Forced Build Properties:

Responsible Users:

1. Darshit Shah

   darnirohnoyoudont@gnu.org

Timing:

All Changes:

:

1. Change #124625

   Category	wget
   Changed by	Darshit Shah <darnirohnoyoudont@gnu.org>
   Changed at	Tue 16 Mar 2021 21:48:13
   Repository	https://gitlab.com/gnuwget/wget.git
   Project	wget
   Branch	master
   Revision	cf788d60e44afb4ac66fcfb12dc51d8d72af9b47

   Comments

   Use a LOG_COMPILER for running fuzz tests
   This prevents needing a special case in the fuzz tests to detect
   valgrind usage and a new exec. Instead, we simply detect the environment
   in a shell script and start the test with valgrind in the first place.
   
   * fuzz/test-runner.sh: New script for running the fuzz tests
   * fuzz/main.c (main): Remove code for re-running under valgrind
   * fuzz/Makefile.am: Set the LOG_COMPILER to test-runner.sh and remember
     to add it to the list of extra files for packaging

   Changed files

   • fuzz/Makefile.am
   • fuzz/main.c
   • fuzz/test-runner.sh