On 10/14/2014 03:25 PM, Antti Nuortimo wrote: >> >>> 140: autotest.at:385 Syntax error >>> autotest >>> 210: autotest.at:1495 parallel syntax error >>> autotest >>> 212: autotest.at:1530 parallel autotest and signal handling >>> autotest >>
>>> 140. autotest.at:385: 140. Syntax error (autotest.at:385): FAILED ( >> autotest.at:385) >> >> Looks like your shell gave a different failure status than the testsuite >> expected, and that in this case the testsuite should be updated to >> tolerate all non-zero status as okay. What shell are you using? >> > > bash version 4.2.37(1)-release, shipped with Debian Wheezy, from an > official Debian repo. No, not what your $SHELL is, but what /bin/sh is. bash doesn't do that. >>> >>> All 2 tests were successful. >>> ./autotest.at:1495: exit code was 0, expected 1 >> >> Hmm. In this case, the syntax error definitely showed up on stderr, but >> your shell kept going with a 0 exit status. That feels more like a bug >> in your shell, maybe? >> > > A bug is the shell is of course possible. My bash is from Debian Wheezy > official repo. > More likely, since you are using Debian, your /bin/sh is dash. > > I'm using bash and started autoconf from bash, but in the case autoconf > would execute dash, I do have dash also installed, so autoconf can execute > it if needed. My dash version is 0.5.7-3 (shipped with Debian Wheezy, from > an official Debian repo). Could very well be a bug in Debian's build of dash, then. It's been a while since I've used a Debian machine though, so it may be a while before I can try and reproduce it. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
