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 B195F3858D3C; Fri, 22 Dec 2023 09:59:03 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B195F3858D3C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1703239143;
	bh=KL6Q+2Uojy55Lp8908OG2UdAUE3tEgDzYIHOKk0iFTM=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=d5XroXVUzacSQUh+N/JTG9181XIy4vlsNeh5tgo03odnGNaTLFveIG4j3wSRg01Uk
	 XkKFzeUmvSwcGO3TwxwVV86MrJt5w3j2L8kKnn21Y0nTZpqZsLLUo9FncmKyOpkuDc
	 ld1VYnwEpjn0TcIzyAyj//fHZVpt00qcKYNrJgNw=
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: Fri, 22 Dec 2023 09:59:02 +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-8OHrmTNFqR@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 #9 from Lipeng Zhu <lipeng.zhu at intel dot com> ---
Since I still can't reproduce the failure on my side :(, just curious, will=
 the
new added 'rwlock' test cases failed on mutex lock?=