Re: [PATCH] * tests/defs [$sh_errexit_works = yes]: Output 'SIGINT' for signal 2.

2011-09-13 Thread Stefano Lattarini
On Tuesday 13 September 2011, Peter Rosin wrote: > Hi! > > Spotted a typo, and pushed this to the testsuite-work branch as obvious > Thanks! Regards, Stefano

[PATCH] * tests/defs [$sh_errexit_works = yes]: Output 'SIGINT' for signal 2.

2011-09-13 Thread Peter Rosin
Hi! Spotted a typo, and pushed this to the testsuite-work branch as obvious: Cheers, Peter 2011-09-13 Peter Rosin * tests/defs [$sh_errexit_works = yes]: Output 'SIGINT' for signal 2. diff --git a/tests/defs b/tests/defs index f1822c8..297e5c0 100644 --- a/tests/defs +++ b/tests/def

[FYI 3/4] {testsuite-work} tests: an explicative comment on signal-related woes

2011-09-13 Thread Stefano Lattarini
* tests/self-check-exit.tap: Add pointer to a bug-autoconf discussion explaining why this test needs to temporarily block SIGINT. --- ChangeLog |7 +++ tests/self-check-exit.tap |5 +++-- 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/ChangeLog b/Change

[FYI 1/4] {testsuite-work} test defs: work around weird ksh behaviour w.r.t. signal handling

2011-09-13 Thread Stefano Lattarini
* tests/defs (is_blocked_signal): Use perl to determine whether a signal is trapped, since trying to do it portably within the shell means opening a nasty can of worms. For more information and background, see:

[FYI 2/4] {testsuite-work} tests: also trap SIGQUIT; other fixes

2011-09-13 Thread Stefano Lattarini
Some shells seems to just ignore SIGQUIT under some circumstances, even when it is not blocked; however, if the signal it trapped, the trap gets correctly executed. * tests/defs [$sh_errexit_works = yes]: Also trap SIGQUIT. Add extensive explanation of why we do so. * tests/self-check-cleanup.tap:

[FYI 4/4] {testsuite-work} self tests: work around 'unset' spurious non-zero return value

2011-09-13 Thread Stefano Lattarini
* tests/self-check-exit.tap ($init): Unset the possibly already unset variable `am_explicit_skips' when the `errexit' shell flag is not yet active, for the benefit of shell that return a non-zero status when unsetting an already-unset variable. --- ChangeLog |8 tests/

[FYI 0/4] {testsuite-work} Workarounds for shell bugs (mostly related to signals and/or Korn shells)

2011-09-13 Thread Stefano Lattarini
Stefano Lattarini (4): test defs: work around weird ksh behaviour w.r.t. signal handling tests: also trap SIGQUIT; other fixes tests: an explicative comment on signal-related woes self tests: work around 'unset' spurious non-zero return value ChangeLog| 38 ++