From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/27320] localedata/gen-locale.sh failure is ignored
Date: Tue, 02 Feb 2021 23:07:12 +0000 [thread overview]
Message-ID: <bug-27320-716-1n8KgpOrkh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27320-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27320
--- Comment #3 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Tue, 2 Feb 2021, hjl.tools at gmail dot com via Glibc-bugs wrote:
> In this particular case, localedata/gen-locale.sh failed because of a bug
> in memmove. I don't think these kinds of failures should be ignored.
The basic principle is: suppose your board falls over (kernel panic etc.)
half way through a test run. It should still produce a toplevel tests.sum
file, with all the tests that couldn't run because the board had fallen
over having their results reported as FAIL.
The failure shouldn't be *ignored* - but it should result in a FAIL and
other tests continuing to run, rather than an early exit from "make
check".
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-02-02 23:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 20:30 [Bug localedata/27320] New: " hjl.tools at gmail dot com
2021-02-02 20:42 ` [Bug localedata/27320] " fweimer at redhat dot com
2021-02-02 21:02 ` hjl.tools at gmail dot com
2021-02-02 23:07 ` joseph at codesourcery dot com [this message]
2021-02-02 23:11 ` hjl.tools at gmail dot com
2021-02-03 8:46 ` schwab@linux-m68k.org
2021-02-03 19:20 ` joseph at codesourcery dot com
2021-02-03 20:13 ` [Bug localedata/27320] localedata/gen-locale.sh failure in native build " hjl.tools at gmail dot com
2021-02-03 21:13 ` joseph at codesourcery dot com
2021-02-03 21:34 ` hjl.tools at gmail dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-27320-716-1n8KgpOrkh@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libc-locales@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).