Subject: |
Re: Build failed in Jenkins: epics-base-3.16-linux32-test #30 |
From: |
Michael Davidsaver <[email protected]> |
To: |
[email protected] |
Date: |
Fri, 4 Mar 2016 18:52:31 -0500 |
FYI I have been able to reproduce this a couple of times.
On 03/04/2016 12:13 PM, Michael Davidsaver wrote:
> On 03/04/2016 11:56 AM, APS Jenkins wrote:
>> src/ioc/db/test/O.linux-x86/dbCaLinkTest.tap .............
>> not ok 14 - == hello
>> Failed 1/99 subtests
> To put this in context. This is effectively failing in the same place
> as previously. The same test is repeated with native and string CA links.
>
>> src/ioc/db/test/O.linux-x86/dbCaLinkTest.tap .............
>> not ok 7 - temp (0) == 42 (42)
>> Failed 1/99 subtests
> Zero and empty string are the previous values of the link, so my attempt
> to wait for for an update is probably racy.
>
- Replies:
- Re: Build failed in Jenkins: epics-base-3.16-linux32-test #30 Michael Davidsaver
- References:
- Build failed in Jenkins: epics-base-3.16-linux32-test #29 APS Jenkins
- Build failed in Jenkins: epics-base-3.16-linux32-test #30 APS Jenkins
- Re: Build failed in Jenkins: epics-base-3.16-linux32-test #30 Michael Davidsaver
- Navigate by Date:
- Prev:
RE: EPICS Base 3.16.0.1 released Williams Jr., Ernest L.
- Next:
Re: Build failed in Jenkins: epics-base-3.16-linux32-test #30 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
2024
2025
- Navigate by Thread:
- Prev:
Re: Build failed in Jenkins: epics-base-3.16-linux32-test #30 Michael Davidsaver
- Next:
Re: Build failed in Jenkins: epics-base-3.16-linux32-test #30 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
2024
2025
|