https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98823
--- 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: > > http://git.savannah.gnu.org/gitweb/?p=dejagnu.git;a=blob;f=lib/remote.exp; > h=1c9971a076415adc2fcdc04ab8f78cc832ce1098;hb=HEAD#l1162 > > 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 the > function refers to the global variable named "timeout", not the parameter > named "timeout". > > This means that although the DejaGNU procedure unix_load appears to set the > timeout to the value of the global variable "test_timeout", and logs various > 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
