On 12/18/2012 01:48 AM, Pádraig Brady wrote: > > So the skip was on purpose and to avoid signal propagation issues seen > on some older systems: > http://git.sv.gnu.org/gitweb/?p=coreutils.git;a=commit;h=v8.14-30-g6603e37 > > This initial failure is worrying, though may be a false positive > due to your shell or something. What versions of dash, bash, kernel > do you have there? >
$ bash --version GNU bash, version 4.2.36(2)-release (i686-pc-linux-gnu) $ dpkg -l dash | sed -n '$p' ii dash 0.5.7-3 i386 POSIX-compliant shell $ uname -rsv Linux 2.6.30-2-686 #1 SMP Sat Sep 26 01:16:22 UTC 2009 > I can't reproduce at all here with any shell, though you might > have older versions. > > What is your system /bin/sh, dash or bash? > Bash. But the affected coreutils testsuite run was done with a more bleeding-edge version of bash, explicitly selected as SHELL (and CONFIG_SHELL). > Note you can force a particular SHELL as follows, > and it would be interesting to see if the issue affected all shells. > The fact is that I haven't been able to reproduce the issue after the first failure. So it won't be easy to ensure whether it has been fixed... > make check TESTS='tests/misc/timeout-group.sh' SUBDIRS=. VERBOSE=yes > SHELL=bash > > Hopefully we can come up with a skip for this case too. > > thanks, > Pádraig. Regards, Stefano
