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: "Tulio Magno Quites Machado Filho" <tuliom at linux dot vnet dot ibm dot com>
- To: Joseph Myers <joseph at codesourcery dot com>, "Carlos O'Donell" <carlos at redhat dot com>
- Cc: 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>
- Cc:
- Date: Wed, 19 Apr 2017 15:00:49 -0300
- 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>
Joseph Myers <joseph@codesourcery.com> writes:
> On Tue, 18 Apr 2017, Carlos O'Donell wrote:
>
>> (b) If your OS and machine port have a buildbot slave, then all maintainers
>> will strive to ensure that their changes do not introduce breakage that
>> shows up on those buildbots, and will work to correct any such breakage.
>
> Buildbots don't provide a way for people to test their patches on those
> buildbots.
This is disabled right now, but we can enable it if we think that's
important:
http://docs.buildbot.net/0.8.9/manual/cfg-schedulers.html#try-schedulers
We have to confirm with BuildSlave owners if they agree with this feature.
However, I think having public logs of the failures already help to find
regressions.
> Also, I'm not aware of anyone monitoring the bots for
> regressions,
I am doing that on POWER. ;-)
> (We also don't have a way for buildbots to send test results to
> libc-testresults, but that would be a peripheral issue if someone were
> monitoring the results for regressions and they actually reliably produced
> results for each testsuite run instead of mysterious errors.)
We can also configure that:
http://docs.buildbot.net/0.8.9/manual/cfg-statustargets.html#mailnotifier
--
Tulio Magno