Re: [FYI 1/2] {test-protocols} tap/awk: handle exit statuses > 256 ( seen on few korn shells)

On 09/28/2011 01:12 PM, Stefano Lattarini wrote: Hi Eric, thanks for the links. On Wednesday 28 September 2011, Eric Blake wrote: On 09/28/2011 08:34 AM, Stefano Lattarini wrote: Some Korn shells, when a child process die due to signal number n, can leave in $? an exit status of 256+n instead

Re: [FYI 1/2] {test-protocols} tap/awk: handle exit statuses > 256 ( seen on few korn shells)

Hi Eric, thanks for the links. On Wednesday 28 September 2011, Eric Blake wrote: > On 09/28/2011 08:34 AM, Stefano Lattarini wrote: > > Some Korn shells, when a child process die due to signal number > > n, can leave in $? an exit status of 256+n instead of the more > > standard 128+n. Apparently

Re: [FYI 1/2] {test-protocols} tap/awk: handle exit statuses > 256 (seen on few korn shells)

On 09/28/2011 08:34 AM, Stefano Lattarini wrote: Some Korn shells, when a child process die due to signal number n, can leave in $? an exit status of 256+n instead of the more standard 128+n. Apparently, both behaviours are allowed by POSIX, Indeed. Here's some further reading: http://austin

[FYI 2/2] {test-protocols} tap/awk: account for unusual korn shell signal handling behaviour

This change has been motivated by a testsuite failure on Debian with the AT&T Korn Shell version 93u-1. * lib/tap-driver.sh: Temporarily ignore some common signals when waiting for the test command to complete, to avoid premature exit in Korn shells that propagate to themselves signals that have k

[FYI 1/2] {test-protocols} tap/awk: handle exit statuses > 256 (seen on few korn shells)

Some Korn shells, when a child process die due to signal number n, can leave in $? an exit status of 256+n instead of the more standard 128+n. Apparently, both behaviours are allowed by POSIX, so be prepared to handle them both. This change has been motivated by a testsuite failure on Debian with

[FYI 0/2] {test-protocols} More fixes for unusual signal handling behaviour of Korn Shells.

Stefano Lattarini (2): tap/awk: handle exit statuses > 256 (seen on few korn shells) tap/awk: account for unusual korn shell signal handling behaviour ChangeLog | 24 lib/tap-driver.sh | 29 + 2 files changed, 49 insertions(+),

New temporary, non-rewindable public branch `aclocal-search-path' (was: Re: [PATCH] aclocal: handle ACLOCAL_PATH environment variable)

On Saturday 24 September 2011, Stefano Lattarini wrote: > [dropping bug-automake] > > The attached patch (for master) is the first step of the testsuite > reorganization. I'd like to apply it to a new public branch > `aclocal-search-path' (to be merged into master eventually). The > patch will s

Re: bug#9578: make uninstall fails after make install-data in empty prefix.

On Monday 26 September 2011, Stefano Lattarini wrote: > On Saturday 24 September 2011, Stefano Lattarini wrote: > > On Thursday 22 September 2011, Nick Bowler wrote: > > > Hello, > > > > > Hi Nick, thanks for the report. > > > > > I noticed a problem testing the uninstall target of my > > > automa

[FYI] {testsuite-work} tests: remove redundant workaround for Solaris /bin/sh

After previous commit `v1.11-1424-g27a399a', some workarounds for Solaris 10 /bin/sh are no more required, and in fact they have started causing XPASS results on Solaris. * tests/tap-signal.tap: Remove unneeded workarounds for Solaris 10 /bin/sh. Some related minor code reorganizations. --- Chan

[FYI] {testsuite-work} tests: fix spurious failures in tests on TAP + signals

* tests/tap-signal.tap: Write the dummy test scripts as perl scripts, not as shell scripts, to work around unportabilities in the handling of signals. In fact, even with bash, the older script were unable to properly deliver a SIGQUIT to themselves consistently. --- ChangeLog|9 ++