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: Florian Weimer <fw at deneb dot enyo dot de>
- Cc: Tulio Magno Quites Machado Filho <tuliom at linux dot vnet dot ibm dot com>, 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: Fri, 21 Apr 2017 19:57:04 +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> <87o9vpvbaw.fsf@mid.deneb.enyo.de>
On Fri, 21 Apr 2017, Florian Weimer wrote:
> * Joseph Myers:
>
> > 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).
>
> Do you agree that the build bots are too difficult to use right now?
>
> I found it very hard to interpret the results, but my difficulties
> baffle others.
I think the mysterious "make[1]: *** [tests] Error 1" at the end of a
large proportion of test runs, with no previous errors reported, is pretty
fatal to simple use of the bots to see what tests are failing. Someone
running a bot showing that issue needs to debug and fix it.
Even with that fixed, it would be a lot better if the bot showed failures
only when there were regressions - that is, if any issues causing known
test failures were fixed, or the tests in question made more robust if
they aren't actually showing glibc bugs, or XFAILed if applicable.
--
Joseph S. Myers
joseph@codesourcery.com