Experimental Physics and Industrial Control System
|
Subject: |
Re: Build failed in Jenkins: epics-base-3.16-linux32-test #29 |
|
From: |
Andrew Johnson <[email protected]> |
|
To: |
<[email protected]> |
|
Date: |
Fri, 4 Mar 2016 10:51:17 -0600 |
When I first saw this email I thought this was just another Windows
failure, but it's not, it's Linux; there may be something racy in
dbCaLinkTest which IIRC was failing on win32 as well (32-bit may be a
hint, not certain of that though).
It's too late to fix in 3.16.0.1 though which I tagged yesterday, I'm
almost finished with the website updates.
On 03/03/2016 07:06 PM, APS Jenkins wrote:
> See <https://jenkins.aps.anl.gov/job/epics-base-3.16-linux32-test/29/>
>
> src/ioc/db/test/O.linux-x86/dbCaLinkTest.tap .............
> not ok 7 - temp (0) == 42 (42)
> Failed 1/99 subtests
- 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-linux32-test #29 APS Jenkins
- Navigate by Date:
- Prev:
Build failed in Jenkins: epics-base-3.16-linux32-test #29 APS Jenkins
- Next:
Build failed in Jenkins: epics-base-3.16-linux32-test #30 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
- Navigate by Thread:
- Prev:
Build failed in Jenkins: epics-base-3.16-linux32-test #29 APS Jenkins
- Next:
Build failed in Jenkins: epics-base-3.16-linux32-test #30 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