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.
