[Insight-developers] tests failed but why ?

[Kent Williams]

It means that your test program raised an exception, or dumped core.  
That's actually good -- an honest core dump is easy to trace, since 
something unmistakably bad happened, loudly.  Much better than silently 
getting the wrong results.

Someone who has access to the system upon which the test failed needs to 
run the test under the debugger, at which point, WHAT happened will be 
quite clear. HOW and WHY it happened, and how it can be fixed, is left 
as an exercise for the reader.

Gaetan Lehmann wrote:

>
> Hi Luis,
>
> Richard have submitted the new revision of the paper, which included 
> some  changes to use the same images in the test and the article, and 
> to verify  the images used in the article.
> The new tests I have added have failed on the insight automatic 
> testing  system, but works without problem on my host.
>
> It would be nice to be able to run the test before validating the  
> submission. For example, a mail can be sent if one are several test 
> have  failed to ask to the author if he want to submit its revision 
> anyway.
>
> Also, the error message is quite non informative "*** Exception 
> executing:  Child aborted". Any idea about how to debug that ?
>
> Regards,
>
> Gaetan
>