Re: hydra and t632

[Thien-Thi Nguyen]

() Efraim Flashner <efraim@flashner.co.il>
() Wed, 21 Oct 2020 21:38:50 +0300

   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.

This tells me that maybe: (a) we are misusing ‘timeout’; or (b)
‘timeout’ is not doing its job.  Do any of the following command
lines result in different behavior?

  timeout --foreground 50s        (original)
  timeout 50s                     (no --foreground)
  LANG=C timeout --foreground 50s (w/ LANG=C)
  LANG=C timeout                  (w/ LANG=C, no --foreground)

The reason for ‘LANG=C’ cases is to see if the number parsing is
sensitive to locale in some weird way (IIRC i saw something
about that changing in the more recent coreutils NEWS file).

Another possiblity is (c) ‘co’ is not detecting the TTY, but that
is doubtful since t632.d/signal-handling-out-and-err has the line

  writable t632.d/x exists; remove it? [ny](n): 

which shows ‘co’ initiating user-interaction, which it only does
if it has detected the TTY.

Hmmm...  i'm hoping for (a), but fear (b) to be the root cause.

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

signature.asc
Description: PGP signature