|
Subject: |
Re: Build failed in Jenkins: epics-base-3.16-linux32-test #30 |
|
From: |
Michael Davidsaver <[email protected]> |
|
To: |
[email protected] |
|
Date: |
Wed, 9 Mar 2016 14:59:37 -0500 |
On 03/09/2016 02:53 PM, Andrew Johnson wrote:
> ...I know you hate polling...
Oh, you noticed :)
> ... can't you set the PV it's monitoring to a known value and just
poll until you see that value ...
Well yes, I suppose so...
- 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
- Re: Build failed in Jenkins: epics-base-3.16-linux32-test #30 Andrew Johnson
- Navigate by Date:
- Prev:
Re: Build failed in Jenkins: epics-base-3.16-linux32-test #30 Andrew Johnson
- Next:
Strict aliasing blog-post 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
2025
- Navigate by Thread:
- Prev:
Re: Build failed in Jenkins: epics-base-3.16-linux32-test #30 Andrew Johnson
- Next:
Jenkins build is back to normal : epics-base-3.16-linux32-test #31 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
2025
| 
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·