https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116701
Hans-Peter Nilsson <hp at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|target |testsuite
--- Comment #1 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
This is a testism. You'll only see this test failing when:
- Testing for a non-fd_truncate target (usually a simulator that can't chsize
or ftruncate, see the effective_target).
- Also testing unsigned_22 in the same run.
- Testing "serially" or "unlucky" with the parallel test run such that
unsigned_22 has run before write_check3.
The cause is that the unsigned_22 test (added in the named commit) leaves an
output file "fort.10", which is picked up by write_check3 which then calls
libgfortran raw_truncate. I guess the gfortran "unit-machinery" wants to clear
that file if it exists.
Some option is needed to make the "fort.10" file name unique or something to
that effect in a way that it isn't picked up by write_check3. A dg- cleanup
function might do, perhaps one exists? A "git grep -w fort" in testsuite/lib
catches nothing though.
