Re: hydra and t632

--==-=-=
Content-Type: multipart/mixed; boundary="=-=-="

--=-=-=
Content-Type: text/plain

() Efraim Flashner <[email protected]>
() Wed, 21 Oct 2020 09:24:38 +0300

Also, we have differing t632.d/signal-handling-out-and-err:


--=-=-=
Content-Type: text/plain
Content-Disposition: inline; filename=signal-handling-out-and-err
Content-Transfer-Encoding: quoted-printable

t632.d/x,v  -->  t632.d/x
revision 1.1 (locked)
writable t632.d/x exists; remove it? [ny](n):=20
RCS: Terminated (Signal sent by kill() 23332 1000)
RCS: Cleaning up.

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


That's the real culprit; actually, the t632.d/out is not checked
in this test.  Sorry about that noise.  The relevant line is:

  timeout --foreground 0.42s co -l -I $w 1>$sout 2>&1

My understanding is that =E2=80=98--foreground=E2=80=99 is necessary for =
=E2=80=98co=E2=80=99 to
read from the TTY.  While it is blocked, waiting for input,
=E2=80=98timeout=E2=80=99 delivers the SIGTERM.

On my system, this wait (0.42s) is (humanly) noticible.  Let's
see about yours.  Could you s/0.42/5.0/ and see if the test
indeed "stalls" for five seconds before completing?

=2D-=20
Thien-Thi Nguyen -----------------------------------------------
 (defun responsep (query)               ; (2020) Software Libero
   (pcase (context query)               ;       =3D Dissenso Etico
     (`(technical ,ml) (correctp ml))
     ...))                              748E A0E8 1CB8 A748 9BFA
=2D-------------------------------------- 6CE4 6703 2224 4C80 7502

--=-=-=--

--==-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iG4EARECAC4WIQR0jqDoHLinSJv6bORnAyIkTIB1AgUCX5BDsBAcdHRuQGdudXZv
bGEub3JnAAoJEGcDIiRMgHUCGDMAoLNhXN+bShSRWzw6MwuzucAyl9P1AJ468cu/
jGDGz182LDO9ghTN3CBqZw==
=bscJ
-----END PGP SIGNATURE-----
--==-=-=--