This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Status of build bots?
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Carlos O'Donell <carlos at redhat dot com>
- Cc: Florian Weimer <fweimer at redhat dot com>, Mark Wielaard <mark at klomp dot org>, libc-alpha <libc-alpha at sourceware dot org>, Tulio Magno Quites Machado Filho <tuliom at linux dot ibm dot com>, Szabolcs Nagy <szabolcs dot nagy at arm dot com>, Stefan Liebler <stli at linux dot ibm dot com>, Siddhesh Poyarekar <siddhesh at gotplt dot org>
- Date: Tue, 20 Aug 2019 21:22:01 +0000
- Subject: Re: Status of build bots?
- Ironport-sdr: /HJQAGQKGKW0L4f2uAeqqkFOvaQjqewDN8escsLv2WmzdXneBtWoausb3fQQf1WuP+k5+tx6uO YDHSqN8iDcaGoL0mRkGmRdmdA437O7Dm6GGmS6dqqO/sbyoBTcaevzSFEdu3NVGeYgxb3JAaFD uJH9GkUPm/x1B8hIbWfDFeHpOn6dg9/hDMZ4poqg9iEwA9HvQ5N5U53SilRjIDwB5Ng2av15Xw ZfE/MoW//aXyN70IBvyPLLcu5QLEHEF5HAOO1O8rlHIp1XJ2cZSKJ2VfjlWRwbMbJE/Zhj9neK dwk=
- Ironport-sdr: 7tGJvBiYZ2aKbUeboIXbiBpVsiXeDNH7W6kTUNLnPuNeg5GqYbY+E6h7L3GDquqIHdO6z8iskF w7kpYAuAvIbHqagGWN5ECm6l3gWkL6ndD+tmgZD21yNWHICAs9oZDXq1rZeLHyWio5qO6bD65g vIxUv4ZqVQqKoasuorHi7Qf7NVZa5DmvCCREW5ASN1gtsMJIcsAJqEmXmbhLfMInSzthBW/s9t eQIA9uE94R9d/hvh20zjioHPO6TXJD4plmGqATF5rxC/UyiK4IeHHSfw6k3+sDpIet8P5bjnUN HjI=
- References: <2ea82ddf-600e-d3db-c3fd-183684d0b173@redhat.com> <ea6cfdf1a0836b22214312dfc9d0d78f7fe5bb58.camel@klomp.org> <a678133b-cbcb-aa00-6ad8-5e6a11fa765d@redhat.com> <87sgpwp2xd.fsf@oldenburg2.str.redhat.com> <eb649fa3-648c-eda6-9a88-ef515a2521a8@redhat.com>
On Tue, 20 Aug 2019, Carlos O'Donell wrote:
> (b) Commit to fixing machine-specific test failures.
> - Machine maintainers get on board to cleanup machine failures as xfails.
We also need to revisit previous decisions to let some tests fail.
Case in point: the known (and documented as such on the wiki) failures of
FAIL: resolv/tst-resolv-ai_idn
FAIL: resolv/tst-resolv-ai_idn-latin1
with libidn2 before version 2.0.5.
Marking as either UNSUPPORTED or XFAIL when using older libidn2 would be
reasonable (I suspect UNSUPPORTED is more practical, since the tests could
dlopen libidn2 and call idn2_check_version). Leaving as FAIL is
unhelpful; it means anyone testing on Ubuntu 18.04, for example, needs to
know to disregard those failures.
Likewise anything else that fails because of some environmental issue that
it's reasonable to have present on a buildbot system - we need to find a
way to make such known issues result in something other than FAIL, so that
the expected results can be clean.
(The other, longstanding, failure I see for native x86_64 testing on
Ubuntu 18.04 is
FAIL: nss/tst-nss-files-hosts-long
.)
--
Joseph S. Myers
joseph@codesourcery.com