From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id D1E753858CDB; Thu,  4 May 2023 12:05:06 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D1E753858CDB
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1683201906;
	bh=HpbdfOVghfCNj0ThiPiqAOtNIMTBJZZimOkdG4uB8NQ=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=dEkUWpLcHFi9Ki8fOsu3GffmwLTvNrgqCZQkk0ETwA6mNKFcAU8Xoq9OZ/E1/gV51
	 L6RkJvQNSbkzPVPjs10kTrevkbe/z6BnZwWUwpEqMRDX3txe+e0cAJyB6C/lF5DjRm
	 ufSp5d7MrTwxKDUDuBihh7k5MZNGZ98eAHRl0lws=
From: "simon.marchi at polymtl dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/30414] Random failure in
 gdb.fortran/lbound-ubound.exp
Date: Thu, 04 May 2023 12:05:06 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: simon.marchi at polymtl dot ca
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-30414-4717-lkivdHB5rs@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-30414-4717@http.sourceware.org/bugzilla/>
References: <bug-30414-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gdb-prs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D30414

--- Comment #5 from Simon Marchi <simon.marchi at polymtl dot ca> ---
(In reply to Tom de Vries from comment #4)
> (In reply to Simon Marchi from comment #3)
> > Hmm it could be.  The gdb_test_multiple reads from both the GDB output =
and
> > the inferior's output, so it is possible that there is a race here, tha=
t we
> > read GDB's prompt before we read the UBOUND line.
>=20
> AFAIU, comment 0 shows the race happening:
> ...
> (gdb) continue
> Continuing.
>=20
> Breakpoint 2, do_test (lb=3D..., ub=3D...) at
> /home/jenkins/workspace/binutils-gdb_master_linuxbuild/platform/jammy-amd=
64/
> target_board/nati
> ve-gdbserver/src/binutils-gdb/gdb/testsuite/gdb.fortran/lbound-ubound.F90=
:45
> 45        print *, ""   ! Test Breakpoint
> (gdb) Remote debugging from host ::1, port 37496
>=20=20
>  Expected GDB Output:
>=20=20
> LBOUND =3D (-8, -10)
> UBOUND =3D (-1, -2)
> APB: Run a test here
> APB: Expected lbound '(-8, -10)'
> APB: Expected ubound ''
> ...
>=20
> My understanding is that we see the order in which expect reads things, a=
nd
> in this snippet the prompt comes before the UBOUND line.

Ah, yes.  I wasn't able to decode the log, but now that you mention it, it
makes sense.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=