Re: ATF confusion with improperly terminated script

[Garrett Cooper <yanegomi%gmail.com@localhost>]

On Sun, Feb 6, 2011 at 3:22 PM, Giorgos Keramidas
<keramida%ceid.upatras.gr@localhost> wrote:
> On Sun, 6 Feb 2011 05:53:54 -0800, Garrett Cooper 
> <yanegomi%gmail.com@localhost> wrote:
>> Hi again Julio, et all,
>>     Until one runs set -x in the script below, it isn't apparent why
>> the script was failing. Is this issue going to be fixed in the future
>> with kyua?
>>
>> Thanks,
>> -Garrett
>>
>> $ atf-run
>> Content-Type: application/X-atf-tps; version="2"
>>
> ...
>> tps-count: 1
>> + [ -z '' ]
>> + echo '${SH} is not set, please correct and re-run.'
>> + exit 1

^^^ This was the first hurdle I had to get over to make progress in
this string of threads; the problem was that I didn't have enough
details to root-cause why things were failing without set -x, as it
was parsing output from stdout. ^^^

>> tp-start: regress.sh, 0
>> tp-end: regress.sh, Invalid format for test case list: 1: Unexpected
>> token `is'; expected `:'
>> info: time.end, Sun Feb 6 05:51:13 PST 2011
>
> What dos the test case shell-script include?
>
> The error message may be pointing in the right direction, but not in a
> very straight-forward way.

The error messages punted back from ATF are unfortunately unhelpful
when dealing with abnormal termination of test suites, in particular
when things puke messages out on stdout.

Thanks!
-Garrett