public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/95546] Random Fortran test failures
Date: Thu, 04 Jun 2020 22:49:18 +0000 [thread overview]
Message-ID: <bug-95546-4-gceWkOHNwk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95546-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95546
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu.org
--- Comment #2 from kargl at gcc dot gnu.org ---
(In reply to H.J. Lu from comment #1)
> It happens with "make -jN check".
The Fortran code is correct.
If 'make -jN check' is trying to build and execute multiple
versions of eof_4.f90 in parallel, then that won't work.
Looks like you have a race condition with parallel make.
next prev parent reply other threads:[~2020-06-04 22:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 22:41 [Bug fortran/95546] New: " hjl.tools at gmail dot com
2020-06-04 22:41 ` [Bug fortran/95546] " hjl.tools at gmail dot com
2020-06-04 22:49 ` kargl at gcc dot gnu.org [this message]
2020-06-04 23:46 ` dominiq at lps dot ens.fr
2020-06-05 15:46 ` [Bug testsuite/95546] " jvdelisle at charter dot net
2020-06-05 17:25 ` sgk at troutmask dot apl.washington.edu
2020-06-05 19:51 ` dominiq at lps dot ens.fr
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-95546-4-gceWkOHNwk@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).