public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/113005] 'libgomp.fortran/rwlock_1.f90', 'libgomp.fortran/rwlock_3.f90' execution test timeouts
Date: Fri, 22 Dec 2023 09:04:34 +0000 [thread overview]
Message-ID: <bug-113005-4-BcZkFf6TYX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113005-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113005
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Execution timeout is: 300
spawn [open ...]
STOP 2
Internal Error: Trying to free nonempty asynchronous unit
Error termination. Backtrace:
Internal Error: Trying to free nonempty asynchronous unit
Error termination. Backtrace:
#0 0x7f986429289e in free_async_unit
at ../../../libgfortran/io/async.c:211
#1 0x7f9864288729 in close_unit_1
at ../../../libgfortran/io/unit.c:759
#2 0x401644 in ???
#3 0x7f986432cd7d in ???
#4 0x7f9863e87c90 in ???
#5 0x7f9863f07fbb in ???
#6 0xffffffffffffffff in ???
FAIL: libgomp.fortran/rwlock_1.f90 -O0 execution test
is what I see in the log. Or just STOP 2.
next prev parent reply other threads:[~2023-12-22 9:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 20:46 [Bug libfortran/113005] New: " tschwinge at gcc dot gnu.org
2023-12-21 11:41 ` [Bug testsuite/113005] " tschwinge at gcc dot gnu.org
2023-12-21 11:47 ` jakub at gcc dot gnu.org
2023-12-21 11:50 ` jakub at gcc dot gnu.org
2023-12-22 6:52 ` lipeng.zhu at intel dot com
2023-12-22 8:48 ` jakub at gcc dot gnu.org
2023-12-22 8:59 ` jakub at gcc dot gnu.org
2023-12-22 9:02 ` jakub at gcc dot gnu.org
2023-12-22 9:04 ` jakub at gcc dot gnu.org [this message]
2023-12-22 9:59 ` lipeng.zhu at intel dot com
2023-12-22 11:14 ` jakub at gcc dot gnu.org
2023-12-25 2:55 ` lipeng.zhu at intel dot com
2023-12-25 6:22 ` lipeng.zhu at intel dot com
2023-12-25 7:31 ` lipeng.zhu at intel dot com
2024-01-22 1:02 ` lipeng.zhu at intel 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-113005-4-BcZkFf6TYX@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).