From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [musl] musl CI?
Date: Tue, 17 Nov 2020 10:48:24 -0500 [thread overview]
Message-ID: <20201117154824.GY534@brightrain.aerifal.cx> (raw)
In-Reply-To: <87eeksqjew.fsf@vuxu.org>
On Tue, Nov 17, 2020 at 01:04:07PM +0100, Leah Neukirchen wrote:
> Rich Felker <dalias@libc.org> writes:
>
> > The topic of CI for testing came up on #musl today, and although it's
> > not something I want to be responsible for running, it does sound very
> > good to have. We noted that libc-test currently has tests that are
> > failing and expected to fail, and that this is normal and not cause
> > for disabling tests, but it did suggest to me a methodology that seems
> > more appropriate than checking whether tests succeed: checking for
> > differences in test output (as well as other things, like symbol
> > table) vs suitable baselines like last release or last run.
>
> The tool abidiff from libabigail may be useful for that:
>
> https://sourceware.org/libabigail/manual/abidiff.html
I seem to recall it coming up before and finding it overkill. Not
objecting if anyone wants to setup something using it and can, but
IIRC nsz has a simple ABI dumper too based on C++ name mangling, and
just the symbol table itself (without any info on further ABI for the
symbols) can be done with nm -D.
Rich
prev parent reply other threads:[~2020-11-17 15:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 4:09 Rich Felker
2020-11-17 6:52 ` Ruinland ChuanTzu Tsai
2020-11-17 15:52 ` Rich Felker
2020-11-17 8:39 ` Ruinland ChuanTzu Tsai
2020-11-17 9:44 ` Arnd Bergmann
2020-11-17 12:04 ` Leah Neukirchen
2020-11-17 15:48 ` Rich Felker [this message]
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=20201117154824.GY534@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).