From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/25908] Race condition in locale tests
Date: Mon, 04 May 2020 15:43:11 +0000 [thread overview]
Message-ID: <bug-25908-716-ognB8ep43Q@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25908-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25908
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |carlos at redhat dot com
--- Comment #1 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to H.J. Lu from comment #0)
> On Linux/x86-64 with heavy load, "make check -jN" got
>
> FAIL: locale/tst-localedef-path-norm
>
> [hjl@gnu-cfl-2 build-x86_64-linux]$ cat locale/tst-localedef-path-norm.out
> error: subprocess failed: execv
> error: expected exit status: 0
> error: actual exit status: 4 [0x400]
> error: subprocess failed: execv
> error: unexpected error output from subprocess
> [error] cannot write output files to `en_US1.UTF-8': No such file or
> directory
Can you reproduce this with a clean build/check?
Commit 6f0baacf0f8920d084c4809ed126ed3e1be34001 invalidates existing
testroot.pristine, and you must start clean otherwise the above test will fail
in an incremental build and check.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-05-04 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 18:12 [Bug localedata/25908] New: " hjl.tools at gmail dot com
2020-05-02 18:15 ` [Bug localedata/25908] " hjl.tools at gmail dot com
2020-05-04 15:43 ` carlos at redhat dot com [this message]
2020-05-04 19:03 ` 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-25908-716-ognB8ep43Q@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).