public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: Nick Alcock <nick.alcock@oracle.com>
To: buildbot@sourceware.org
Cc: binutils@sourceware.org
Subject: adding make check-libctf to binutils trybot?
Date: Thu, 18 Apr 2024 17:32:33 +0100	[thread overview]
Message-ID: <87a5lqvdge.fsf@esperi.org.uk> (raw)

I'm getting back to libctf development again (some fairly big things
coming, I hope), so I've just tried the trybots for the first time.

First impressions: really useful to be able to test on piles of arches
without needing to set up dead slow QEMU emulations of them myself;
might be even more useful if FAILs/ERRORs were explicitly filtered into
their own category rather than carefully filtering out warnings (which
are usually useless junk from dejagnu), while you have to explicitly
download the stdio output to figure out which testsuite any failures
actually happened in...

... but the check-libctf tests are not run at all, which means the only
testing I get of libctf is of its interoperation with ld, which is only
about half the codebase and about as much of the API surface (counting
uses internal to libctf itself).

So... could make check-libctf be added to the stuff routinely run when
binutils try-builds are done? I'd write a patch but I'm not honestly
sure where the repo is or anything :) it's pretty fast (much faster than
make check-ld, about as fast as the gas tests) and doesn't have spurious
failures anywhere that I know of. (And if there are failures, I'll fix
them.)

Thanks!

-- 
NULL && (void)

                 reply	other threads:[~2024-04-18 16:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a5lqvdge.fsf@esperi.org.uk \
    --to=nick.alcock@oracle.com \
    --cc=binutils@sourceware.org \
    --cc=buildbot@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).