https://gcc.gnu.org/bugzilla/show_bug.cgi?id=125584
Bug ID: 125584
Summary: gfortran.dg/corray tests may use excessive space in
/tmp
Product: gcc
Version: 17.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
CC: vehre at gcc dot gnu.org
Target Milestone: ---
During gfortran.dg/coarray testing on Solaris, I've several times noticed that
the tests consume excessive space in /tmp (tmpfs), often 16 GB.
It turns out that quite a number of these tests allocate 256 MB shared memory
segments. Those are backed up by files in below /tmp/.LIBRT/SHM. Currently,
each test runs 8 processes in parallel, as set via GFORTRAN_NUM_IMAGES in
caf.exp, for a total of 2 GB.
During parallel testsuite runs, this can easily lead to excessive /tmp usage.
I wonder what to do here: when I reduced GFORTRAN_NUM_IMAGES to 4 just as
an experiment, only a single test FAILed:
FAIL: gfortran.dg/coarray/deallocate_sync.f90 -fcoarray=lib -O2 -lcaf_shmem
execution test
Once could either inhibit parallel testing completely for caf.exp or follow
what libgomp does in libgomp/testsuite/lib/libgomp.exp. As it is, parallel
testcases can easily add unexpected resource consumption during testsuite runs.
