[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: hydra and t632

From: Efraim Flashner
Subject: Re: hydra and t632
Date: Wed, 21 Oct 2020 21:38:50 +0300

On Wed, Oct 21, 2020 at 10:20:31AM -0400, Thien-Thi Nguyen wrote:
> () Efraim Flashner <efraim@flashner.co.il>
> () Wed, 21 Oct 2020 09:24:38 +0300
> Also, we have differing t632.d/signal-handling-out-and-err:

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

> 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 ‘--foreground’ is necessary for ‘co’ to
> read from the TTY.  While it is blocked, waiting for input,
> ‘timeout’ 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?

I didn't see any stalling at all so I changed it to 50s and it
still finished immediately. I thought there might not be a tty in the
build environment but I see in the setup code there is a /dev/tty. It
looks like it's bind-mounted from outside the build chroot.

Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

Attachment: signature.asc
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]