Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201117040951.GA9668@brightrain.aerifal.cx>
Date: Mon, 16 Nov 2020 23:09:52 -0500
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: musl CI?

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.

I don't think anyone has concrete plans for going forward with this
yet, but I'm posting the outcome so far here for further discussion
and so it's not lost.

Rich

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.