* Stefano Lattarini wrote on Mon, Sep 06, 2010 at 09:22:51PM CEST: > On Monday 06 September 2010, Ralf Wildenhues wrote: > > * Stefano Lattarini wrote on Mon, Sep 06, 2010 at 05:06:23PM CEST: > > That also means, that we should probably be more cautious with > > removing `|| Exit 1' instances from tests.
> Why? The exit trap is currently not installed if a broken /bin/sh > is detected, is it? Ah right, thanks for reminding me of that. > > Or, here's a different idea: maybe we can somehow detect this shell > > feature at run time. In that case it is sufficient to just *not* > > exit from within the trap (unless the trap code has caused another > > failure status that should be reported). > What about my pending patch "Testsuite: use $SHELL to run tests which > are shell scripts."? I'll reply in that thread. > That should ensure that the tests are run with > a decent shell. Maybe we could then hack Automake's configure.ac to > ensure that configure reject shells exhibiting the trap bug. What is > the status of ksh on Tru64/OSF 5.1? Is it as broek as /bin/sh, or is > it usable for our purposes? It does not have this particular issue. And yes, that might be a good strategy indeed; but it shouldn't be developed in the pot-primary branch (only maybe merged in later). Thanks, Ralf
