Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019 
<== Date ==> <== Thread ==>

Subject: Re: Build failed in Jenkins: epics-base-3.16-mac-test #42
From: Andrew Johnson <anj@aps.anl.gov>
To: <core-talk@aps.anl.gov>
Date: Tue, 16 Feb 2016 17:17:03 -0600
On 02/16/2016 04:03 PM, Michael Davidsaver wrote:
> On 02/16/2016 04:03 PM, APS Jenkins wrote:
>> Test Summary Report
>> -------------------
>> src/ioc/db/test/O.darwin-x86/callbackTest.tap           (Wstat: 0 Tests: 339 Failed: 12)
>>   Failed tests:  306-317
>> Files=72, Tests=9409,  2 wallclock secs ( 0.67 usr  0.05 sys +  0.13 cusr  0.11 csys =  0.96 CPU)
>> Result: FAIL
>> Build step 'Execute shell' marked build as failure
> 
> Ok, this one looks like a transient "error" due to system load.

Yup, that's partly why I gave it a separate -test job, so it's quick to
re-run the tests manually without having to rebuild.

>> not ok 306 - delay 11.25 seconds, callback time error |0.8907| < 0.05
>> not ok 307 - delay 11.25 seconds, callback time error |0.8906| < 0.05
>> not ok 308 - delay 11.25 seconds, callback time error |0.8904| < 0.05
>> not ok 309 - delay 11.50 seconds, callback time error |0.6407| < 0.05
>> not ok 310 - delay 11.50 seconds, callback time error |0.6406| < 0.05
>> not ok 311 - delay 11.50 seconds, callback time error |0.6404| < 0.05
>> not ok 312 - delay 11.75 seconds, callback time error |0.3907| < 0.05
>> not ok 313 - delay 11.75 seconds, callback time error |0.3906| < 0.05
>> not ok 314 - delay 11.75 seconds, callback time error |0.3904| < 0.05
>> not ok 315 - delay 12.00 seconds, callback time error |0.1407| < 0.05
>> not ok 316 - delay 12.00 seconds, callback time error |0.1406| < 0.05
>> not ok 317 - delay 12.00 seconds, callback time error |0.1404| < 0.05

0.89 seconds is an 8% over-run. We could change the tests to 10%, but I
wonder if this kind of thing is worth failing over at all?

- Andrew

-- 
There are only two hard problems in distributed systems:
  2. Exactly-once delivery
  1. Guaranteed order of messages
  2. Exactly-once delivery
 -- Mathias Verraes

References:
Build failed in Jenkins: epics-base-3.16-mac-test #42 APS Jenkins
Re: Build failed in Jenkins: epics-base-3.16-mac-test #42 Michael Davidsaver

Navigate by Date:
Prev: Jenkins build is back to normal : epics-base-3.16-mac-test #43 APS Jenkins
Next: Re: Small bug in 3.16 Andrew Johnson
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019 
Navigate by Thread:
Prev: Re: Build failed in Jenkins: epics-base-3.16-mac-test #42 Michael Davidsaver
Next: Jenkins build is back to normal : epics-base-3.16-mac-test #43 APS Jenkins
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019 
ANJ, 18 Feb 2016 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·