This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Basic requirements for supporting OS and machine ports.
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Tulio Magno Quites Machado Filho <tuliom at linux dot vnet dot ibm dot com>
- Cc: Carlos O'Donell <carlos at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>, Szabolcs Nagy <szabolcs dot nagy at arm dot com>, Richard Henderson <rth at redhat dot com>, Mike Frysinger <vapier at gentoo dot org>, Andreas Schwab <schwab at suse dot de>, Chris Metcalf <cmetcalf at mellanox dot com>, Chung-Lin Tang <chunglin_tang at mentor dot com>, Steven Munroe <sjmunroe at us dot ibm dot com>, Andreas Krebbel <krebbel at linux dot vnet dot ibm dot com>, David Miller <davem at davemloft dot net>, Siddhesh Poyarekar <siddhesh at gotplt dot org>, Florian Weimer <fweimer at redhat dot com>, Aurelien Jarno <aurelien at aurel32 dot net>, Adam Conrad <adconrad at 0c3 dot net>
- Date: Thu, 20 Apr 2017 16:11:56 +0000
- Subject: Re: Basic requirements for supporting OS and machine ports.
- Authentication-results: sourceware.org; auth=none
- References: <c501b05e-3ae1-5bc8-b5a7-b6c2dabb98bc@redhat.com> <alpine.DEB.2.20.1704191505450.28423@digraph.polyomino.org.uk> <87o9vs1dm6.fsf@totoro.br.ibm.com> <alpine.DEB.2.20.1704192139570.9217@digraph.polyomino.org.uk> <87lgqv16b5.fsf@totoro.br.ibm.com>
On Thu, 20 Apr 2017, Tulio Magno Quites Machado Filho wrote:
> > Well, we need a glibc-specific script to collect whatever information we
> > think is relevant from the results of a test run for sending to
> > libc-testresults (for use for both manual and buildbot builds).
>
> Usually BuildBot would notify a build failed and send a link to the place
> where you could get more information, including log files. So it wouldn't
> be necessary to send all of that data to the mailing list.
I think buildbot logs have disappeared at least once when the bot moved
from one system to another. That's a clear reason to send the key
information to the mailing list, so it stays available.
> But it seems you want a much broader solution. Could you elaborate what you'd
> like to see in those messages?
Key information about the compile-time configuration of glibc, such as
configure options, glibc host, GCC and binutils versions, glibc commit
being tested.
Key information about the test configuration, such as the run-built-tests
value and the kernel version on the host used for testing if
run-build-tests is yes.
A list of the tests with unexpected results (anything that's not PASS or
XFAIL) and the numbers of each result, as at the end of the output of
"make check".
I think that's the basic minimum. It would be expected that when doing
pre-release testing for an architecture you send the results to
libc-testresults and include a link on the per-release wiki page. Bots,
whether or not linked to the buildbot master, would also send results to
libc-testresults.
It should be possible for people to grep a libc-testresults mailbox to see
"is this test failing for other people, and if so, in what
configurations?". (Which is a use I make of gcc-testresults from time to
time.)
--
Joseph S. Myers
joseph@codesourcery.com