[BIOSAL] Travis and failure

[Boisvert, Sebastien]

> From: George K. Thiruvathukal [gkt at cs.luc.edu]
> Sent: Thursday, November 13, 2014 2:56 PM
> To: Boisvert, Sebastien
> Subject: Re: Travis and failure
> 
> 
> 
> 
> ​Hi there!
> 
> 
> I think the problem is that the failure is not being reflected as a Unix error code (non-zero). Is it possible that your wrapper for the JUnit results is not returning a non-zero code when tests fail?

The link I gave to you is for the project "Mean.js".

Also, I can confirm to you that "make tests" always returns 0.

The result is available in *junit.xml. Or you can simply grep for "FAILED" in stdout.

No FAILED string means it worked.

> 
> George​
> 
> 
> 
> George K. Thiruvathukal, PhD
> 
> Professor of Computer Science, Loyola University Chicago
> 
> Director, Center for Textual Studies and Digital Humanities
> Guest Faculty, Argonne National Laboratory, Math and Computer Science Division
> Editor in Chief, Computing in
>  Science and Engineering (IEEE CS/AIP)
> 
> (w) gkt.tv (v)
>  773.829.4872
> 
> 
> 
> 
> 
> 
> 
> On Thu, Nov 13, 2014 at 2:54 PM, Boisvert, Sebastien 
> <boisvert at anl.gov> wrote:
> 
> If you look at the following build:
> https://travis-ci.org/meanjs/mean/jobs/40710659
> 
> it is written "passed" in green.
> 
> Yet, if you look closely, the log file says:
> 
>  13 passing (3s)
> 1 failing
> 
> 1) Article Model Unit Tests: Method Save should be able to save without problems:
> Error: timeout of 2000ms exceeded
> at null.<anonymous> (/home/travis/build/meanjs/mean/node_modules/mocha/lib/runnable.js:158:19)
> at Timer.listOnTimeout [as ontimeout] (timers.js:112:15)
> 
> 
> 
> I am not sure what is going on there.
> 
> 
>