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 ED2C93894432; Thu, 22 Apr 2021 12:46:27 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org ED2C93894432
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/98823] go testsuite and timeouts
Date: Thu, 22 Apr 2021 12:46:27 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 11.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-98823-4-4jAkPJ6Y1w@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-98823-4@http.gcc.gnu.org/bugzilla/>
References: <bug-98823-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
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Apr 2021 12:46:28 -0000

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

--- Comment #16 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Ian Lance Taylor from comment #11)
> I'm just noting that DejaGNU appears to have a bug in the standard_wait
> procedure:
>=20
> http://git.savannah.gnu.org/gitweb/?p=3Ddejagnu.git;a=3Dblob;f=3Dlib/remo=
te.exp;
> h=3D1c9971a076415adc2fcdc04ab8f78cc832ce1098;hb=3DHEAD#l1162
>=20
> The code seems to assume that the parameter timeout will set the timeout =
for
> the remote_expect.  But as far as I can tell, when running under expect,
> "timeout" is always a global variable.  So the $timeout that appears in t=
he
> function refers to the global variable named "timeout", not the parameter
> named "timeout".
>=20
> This means that although the DejaGNU procedure unix_load appears to set t=
he
> timeout to the value of the global variable "test_timeout", and logs vari=
ous
> messages to that effect, in fact that variable has no effect.  Only the
> variable "timeout" matters.

I raised this on the DG mailing list a few months ago, see:
https://lists.gnu.org/archive/html/dejagnu/2020-12/msg00000.html
It's actually GCC's fault for monkeypatching the standard_wait proc:
https://lists.gnu.org/archive/html/dejagnu/2020-12/msg00003.html=