public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/65107] New: FAIL: gfortran.dg/eof_4.f90, runtime error: File 'test.dat' already exists
Date: Wed, 18 Feb 2015 13:54:00 -0000 [thread overview]
Message-ID: <bug-65107-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65107
Bug ID: 65107
Summary: FAIL: gfortran.dg/eof_4.f90, runtime error: File
'test.dat' already exists
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: vries at gcc dot gnu.org
failure in gfortran.sum:
...
FAIL: gfortran.dg/eof_4.f90 -O0 execution test
FAIL: gfortran.dg/eof_4.f90 -O1 execution test
FAIL: gfortran.dg/eof_4.f90 -O2 execution test
FAIL: gfortran.dg/eof_4.f90 -O3 -fomit-frame-pointer execution test
FAIL: gfortran.dg/eof_4.f90 -O3 -fomit-frame-pointer -funroll-all-loops
-finline-functions execution test
FAIL: gfortran.dg/eof_4.f90 -O3 -fomit-frame-pointer -funroll-loops
execution test
FAIL: gfortran.dg/eof_4.f90 -O3 -g execution test
FAIL: gfortran.dg/eof_4.f90 -Os execution test
...
In more detail:
...
At line 12 of file src/gcc/testsuite/gfortran.dg/eof_4.f90 (unit = 99)
Fortran runtime error: File 'test.dat' already exists
FAIL: gfortran.dg/eof_4.f90 -O0 execution test
...
Probably observed earlier here: PR64770 comment 0.
The nature of the failure is that the test expects test.dat not to exist, but
it does.
The test itself does not clean up after itself, so it's missing:
...
! { dg-final { remote_file build delete "test.dat" } }
...
But cleaning after itself does not guarantee that this failure is fixed. We
need to ensure that all tests that use test.dat clean up after themselves.
next reply other threads:[~2015-02-18 13:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 13:54 vries at gcc dot gnu.org [this message]
2015-02-18 14:28 ` [Bug testsuite/65107] " dominiq at lps dot ens.fr
2015-02-18 16:32 ` vries at gcc dot gnu.org
2015-02-18 20:08 ` vries at gcc dot gnu.org
2015-02-21 0:32 ` vries at gcc dot gnu.org
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-65107-4@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).