Setting up Binutils workers/builders on Solaris

Frank Ch. Eigler fche@elastic.org
Sat Jun 6 14:08:30 GMT 2026


Hi -

> * In my local testing, I've always run make -k -j<N> check as is
>   customary to avoid failure of one testsuite to break the others.  This
>   is what happens here: make check-gprof fails, so the two others
>   (libctf, libsframe) aren't even run though they pass just fine
>   locally.

Agreed, -k makes sense, added.

> * gprof, unlike the others, doesn't use a DejaGnu testsuite, but one of
>   its own.  So failure to build or run the tests causes make check to
>   fail.

Yeah.

> * In my own testing, I've always used the toplevel mail-report.log
>   target, which runs contrib/test_summary -t, to generate a easy to
>   digest report of testsuite results, as is done over in gcc.  The gprof
>   failures didn't show up there as FAILs, so this went unnoticed.

FWIW, bunsen is a more thorough & useful sink for all the testsuite
data (including non-dejagnu), and it's automatically collected from
our buildbot runs.

- FChE


More information about the Buildbot mailing list