Subject: |
Re: Build failed in Jenkins: epics-base-3.16-linux32-test #13 |
From: |
Andrew Johnson <[email protected]> |
To: |
<[email protected]> |
Date: |
Fri, 12 Feb 2016 11:33:58 -0600 |
Hi Michael,
On 02/12/2016 11:06 AM, APS Jenkins wrote:
> src/std/rec/test/O.linux-x86/arrayOpTest.tap ............. ok
> src/std/rec/test/O.linux-x86/asTest.tap .................. ok
> Bailout called. Further testing stopped: testMonitorWait() exceeds timeout
> FAILED--Further testing stopped: testMonitorWait() exceeds timeout
My fix was just to re-run the tests; given that this failure has
happened before on a different architecture, I think the 10 second
timeout delay in testMonitorWait() is just too short for a busy build
slave. Since the effect of failure is to kill all further testing I have
bumped it all the way up to 60 seconds.
- 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
- Replies:
- Re: Build failed in Jenkins: epics-base-3.16-linux32-test #13 Michael Davidsaver
- References:
- Build failed in Jenkins: epics-base-3.16-linux32-test #13 APS Jenkins
- Navigate by Date:
- Prev:
Jenkins build is back to normal : epics-base-3.16-linux32-test #14 APS Jenkins
- Next:
Bug in dbGet() with server-side plugins Andrew Johnson
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
<2016>
2017
2018
2019
2020
2021
2022
2023
- Navigate by Thread:
- Prev:
Jenkins build is back to normal : epics-base-3.16-linux32-test #14 APS Jenkins
- Next:
Re: Build failed in Jenkins: epics-base-3.16-linux32-test #13 Michael Davidsaver
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
<2016>
2017
2018
2019
2020
2021
2022
2023
|