testsuite timeout failure is non-obvious

[Michael Banck]

It took me a long time to figure out the issue of fast/t29 on the armel Debian autobuilder:

https://buildd.debian.org/status/fetch.php?pkg=abinit&arch=armel&ver=8.8.4-1&stamp=1545666770&raw=0

This is the output I get:

[fast][t28][np=1]: succeeded [file=t28o_TIM2_GEO]
Command   /home/mbanck/src/abinit-8.8.4/src/98_main/abinit < /home/mbanck/src/abinit-8.8.4/tests/Test_suite/fast_t27-t28-t29/t29.stdin > /home/mbanck/src/abinit-8.8.4/tests/Test_suite/fast_t27-t28-t29/t29.stdout 2> /home/mbanck/src/abinit-8.8.4/tests/Test_suite/fast_t27-t28-t29/t29.stderr
 returned exit_code: 124

[fast][t29][np=1]: fldiff.pl fatal error:
The diff analysis cannot be done: the number of lines to be analysed differ.
File /home/mbanck/src/abinit-8.8.4/tests/fast/Refs/t29.out: 977 lines, 66 ignored
File /home/mbanck/src/abinit-8.8.4/tests/Test_suite/fast_t27-t28-t29/t29.out: 976 lines, 66 ignored [file=t29.out]
[fast][t29][np=1]: fldiff.pl fatal error:
Unable to open input file /home/mbanck/src/abinit-8.8.4/tests/Test_suite/fast_t27-t28-t29/t29o_TIM8_GEO [file=t29o_TIM8_GEO]
[fast][t29][np=1]Test was not expected to fail but subprocesses returned 124
No YAML Error found in [fast][t29][np=1]

In reality, the test ran longer than 15 minutes, the default timeout. Only after I saw the timeout 900 command on the command-line did I figure out the test might have been killed that way.

I think it would be useful if that was made much explicit in the output.