Util-Linux package development
 help / color / mirror / Atom feed
From: Ruediger Meier <sweet_f_a@gmx.de>
To: util-linux@vger.kernel.org
Subject: script, broken test options/return
Date: Thu, 2 Jul 2015 02:03:21 +0200	[thread overview]
Message-ID: <201507020203.21632.sweet_f_a@gmx.de> (raw)

Hi,

on my system (interactive bash on openSUSE 13.1) the "return" subtest 
of "script/options" is broken since 54c6611d.

Seems that input from /dev/null makes the difference. Reproduce like
this:

$ export SCRIPT_DEBUG=all 
$ ./script --command "exit 1" out_good >/dev/null            2>dbg_good
$ ./script --command "exit 1" out_bad  >/dev/null </dev/null 2>dbg_bad
^C <abort ctrl-C>

$ head -n 20 dbg_good dbg_bad
==> dbg_good <==
25703: script:       IO: master fd: 3
25703: script:   SIGNAL: signal fd=5
25703: script:     POLL: calling poll()
25703: script:     POLL: poll() rc=1
25703: script:     POLL:  active pfd[signal].fd=5 POLLIN
25703: script:   SIGNAL: signal FD 5 active
25703: script:     MISC: waiting for child
25703: script:     POLL: calling poll()
25703: script:     POLL: poll() rc=0
25703: script:     POLL: setting die=1
25703: script:     POLL: poll() done
25703: script:     MISC: done!

==> dbg_bad <==
25708: script:       IO: master fd: 3
25708: script:   SIGNAL: signal fd=5
25708: script:     POLL: calling poll()
25708: script:     POLL: poll() rc=1
25708: script:     POLL:  active pfd[stdin].fd=0 POLLIN
25708: script:       IO: 0 FD active
25708: script:     POLL: calling poll()
25708: script:     POLL: poll() rc=1
25708: script:     POLL:  active pfd[stdin].fd=0 POLLIN
25708: script:       IO: 0 FD active
25708: script:     POLL: calling poll()
25708: script:     POLL: poll() rc=1
25708: script:     POLL:  active pfd[stdin].fd=0 POLLIN
25708: script:       IO: 0 FD active
25708: script:     POLL: calling poll()
25708: script:     POLL: poll() rc=1
25708: script:     POLL:  active pfd[stdin].fd=0 POLLIN
25708: script:       IO: 0 FD active
25708: script:     POLL: calling poll()
25708: script:     POLL: poll() rc=1
...

cu,
Rudi

             reply	other threads:[~2015-07-02  0:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-02  0:03 Ruediger Meier [this message]
2015-07-02  8:23 ` script, broken test options/return Karel Zak
2015-07-02  8:32 ` Karel Zak
2015-07-02 10:06   ` Ruediger Meier
2015-07-02 10:10     ` [PATCH] script: evaluate errno only if read() sets it Ruediger Meier
2015-07-02 10:21       ` Ruediger Meier
2015-07-03  8:04         ` Karel Zak
2015-07-03 10:33           ` Ruediger Meier
2016-02-12 16:23     ` [PATCH] tests: mkfs.ext3 image-file needs option -F Ruediger Meier
2016-02-12 16:25       ` Ruediger Meier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201507020203.21632.sweet_f_a@gmx.de \
    --to=sweet_f_a@gmx.de \
    --cc=util-linux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox