Subject: |
Re: Build failed in Jenkins: epics-base-3.16-linux32-test #13 |
From: |
Michael Davidsaver <[email protected]> |
To: |
[email protected] |
Date: |
Mon, 15 Feb 2016 20:49:16 -0500 |
On 02/15/2016 08:19 PM, Michael Davidsaver wrote:
> That "-1" stands out. So far the only candidate I see is in
> dbCaPutLinkCallback() if the target link isn't connected or writable.
> Which would mean that the main thread is racing the dbCa thread to
> CA_CONNECT this link.
Ok, this is it. So the obvious fix is to use/abuse caLink::monitor to
wait for the link to connect.
- Replies:
- Re: Build failed in Jenkins: epics-base-3.16-linux32-test #13 Andrew Johnson
- References:
- Build failed in Jenkins: epics-base-3.16-linux32-test #13 APS Jenkins
- Re: Build failed in Jenkins: epics-base-3.16-linux32-test #13 Andrew Johnson
- Re: Build failed in Jenkins: epics-base-3.16-linux32-test #13 Michael Davidsaver
- Re: Build failed in Jenkins: epics-base-3.16-linux32-test #13 Andrew Johnson
- Re: Build failed in Jenkins: epics-base-3.16-linux32-test #13 Michael Davidsaver
- Navigate by Date:
- Prev:
Re: Build failed in Jenkins: epics-base-3.16-linux32-test #13 Michael Davidsaver
- Next:
Re: Build failed in Jenkins: epics-base-3.16-linux32-test #13 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:
Re: Build failed in Jenkins: epics-base-3.16-linux32-test #13 Michael Davidsaver
- Next:
Re: Build failed in Jenkins: epics-base-3.16-linux32-test #13 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
|