Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87eeksqjew.fsf@vuxu.org>
Date: Tue, 17 Nov 2020 13:04:07 +0100
From: Leah Neukirchen <leah@...u.org>
To: Rich Felker <dalias@...c.org>
Cc: musl@...ts.openwall.com
Subject: Re: musl CI?

Rich Felker <dalias@...c.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

-- 
Leah Neukirchen  <leah@...u.org>  https://leahneukirchen.org/

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.