From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 6868B3858C5F; Mon, 25 Dec 2023 02:55:42 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6868B3858C5F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1703472942;
	bh=ZQvA+jW0R3Qc9ob0WiGN6VTGu+lRoyu8sqWn+CKnE3I=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=n2z+mgkiaLotYblnfbyyVRR9i5KmeCgDHcdVtLAPxkyaGo01CTOQzPzeONiCTJIOt
	 sHHPUFSKwHCFwIwIDa6A/BTCeU85F5viSmnLA7lfqve0E+C/qoIRDtu6dUCbFTwnpv
	 oWhTDmDzLNoOyB5QmQKghJxxYwUYo3EyUewwfJH8=
From: "lipeng.zhu at intel dot com" <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: Mon, 25 Dec 2023 02:55:40 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: testsuite-fail
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lipeng.zhu at intel dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-113005-4-Z6usYv6AEs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113005-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113005-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113005

--- Comment #11 from Lipeng Zhu <lipeng.zhu at intel dot com> ---
(In reply to Jakub Jelinek from comment #10)
>For what I can reproduce on my box (rwlock_1.exe built in the
>x86_64-pc-linux-gnu/libgomp/testsuite subdirectory using the -O0
>compilation line from libgomp*/*.sep:
>$ OMP_NUM_THREADS=3D4096 LD_LIBRARY_PATH=3D../.libs/ time ./rwlock_1.exe
>
> Error termination. Backtrace:
> At line 17 of file
> /home/jakub/src/gcc/libgomp/testsuite/libgomp.fortran/rwlock_1.f90 (unit =
=3D
> 1180)
> Fortran runtime error: Cannot open file '***_tst.dat': Too many open files
>=20
>=20
> With OMP_NUM_THREADS=3D512 it works.

I can reproduce the "Too many open files" error on my local.
The error is caused by the limited open files setting.=20
$ ulimit -n
In existing rwlock test case, it will maintain a fd for each thread, with
OMP_NUM_THREADS growing, it reached the system limitation.=20

>Anyway: should these test cases be limiting themselves to some lower
> 'OMP_NUM_THREADS', for example via 'num_threads' clauses?

This proposal could avoid this kind of issue.=