On 02/08/2016 06:55 PM, APS Jenkins wrote:
> See <https://jenkins.aps.anl.gov/job/epics-base-3.16/57/changes>
So what happened here was that in src/std/rec/test the
linkRetargetLinkTest code called testMonitorWait() but for some reason
that timed out after 10 seconds and aborted the test program. When I
re-ran the test (using the same binary) this afternoon it succeeded, so
this failure was probably only a transient thing which I hope won't
occur again. We'll see when I commit a fix for the Windows build issues...
- 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:
- Jenkins build became unstable: epics-base-3.16 #57 APS Jenkins
- Navigate by Date:
- Prev:
Build failed in Jenkins: epics-base-3.16-win32s #56 APS Jenkins
- Next:
Re: Build failed in Jenkins: epics-base-3.16-win64 #52 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
2024
- Navigate by Thread:
- Prev:
Jenkins build became unstable: epics-base-3.16 #57 APS Jenkins
- Next:
Jenkins build is back to stable : epics-base-3.16 #58 APS Jenkins
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
<2016>
2017
2018
2019
2020
2021
2022
2023
2024
|