Subject: |
Re: Build failed in Jenkins: epics-base-3.16-linux32-test #30 |
From: |
Andrew Johnson <[email protected]> |
To: |
<[email protected]> |
Date: |
Wed, 9 Mar 2016 13:53:21 -0600 |
On 03/09/2016 01:43 PM, Michael Davidsaver wrote:
> I think the issue is that the test is not waiting for the initial
> monitor update to be delivered. It later does wait for an update to be
> delivered, which is assumed to be the result of a dbPutField().
OK; since this is just for test purposes, can't you set the PV it's
monitoring to a known value and just poll until you see that value (or
eventually timeout and abort). I know you hate polling, but this is only
a test program so it doesn't need high performance.
- 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 #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
- Re: Build failed in Jenkins: epics-base-3.16-linux32-test #30 Michael Davidsaver
- Re: Build failed in Jenkins: epics-base-3.16-linux32-test #30 Michael Davidsaver
- Navigate by Date:
- 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
- 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
|