We’d probably all forgotten about this bug which resulted from the monotonic clock changes. I had modified epicsEventTest to add checks for event timeouts that return early, and earlier today I committed and pushed that change so I could work on something else. These tests fail on RTEMS, VxWorks and evidently also on Windows.
On Mar 12, 2020, at 3:21 PM, APS Jenkins via Core-talk <core-talk at aps.anl.gov> wrote:
>
> epicsEventTest.tap ...........
> not ok 18 - epicsEventWaitWithTimeout(0.031250) delay error -0.000250 sec
> not ok 21 - epicsEventWaitWithTimeout(0.003906) delay error -0.003906 sec
> not ok 23 - epicsEventWaitWithTimeout(0.000977) delay error -0.000977 sec
> not ok 24 - epicsEventWaitWithTimeout(0.000488) delay error -0.000488 sec
> not ok 25 - epicsEventWaitWithTimeout(0.000244) delay error -0.000244 sec
> not ok 26 - epicsEventWaitWithTimeout(0.000122) delay error -0.000122 sec
> not ok 27 - epicsEventWaitWithTimeout(0.000061) delay error -0.000061 sec
> not ok 28 - epicsEventWaitWithTimeout(0.000031) delay error -0.000031 sec
> not ok 29 - epicsEventWaitWithTimeout(0.000015) delay error -0.000015 sec
> not ok 30 - epicsEventWaitWithTimeout(0.000008) delay error -0.000008 sec
> not ok 31 - epicsEventWaitWithTimeout(0.000004) delay error -0.000004 sec
> Failed 11/37 subtests
The above shows just the failures. Here are the full set of results from RTEMS-pc386-qemu as a reminder:
> ok 12 - epicsEventWaitWithTimeout(0.000000) delay error 0.000299 sec
> not ok 13 - epicsEventWaitWithTimeout(1.000000) delay error -0.000092 sec
> ok 14 - epicsEventWaitWithTimeout(0.500000) delay error 0.000009 sec
> not ok 15 - epicsEventWaitWithTimeout(0.250000) delay error -0.009993 sec
> not ok 16 - epicsEventWaitWithTimeout(0.125000) delay error -0.005004 sec
> not ok 17 - epicsEventWaitWithTimeout(0.062500) delay error -0.002527 sec
> not ok 18 - epicsEventWaitWithTimeout(0.031250) delay error -0.011118 sec
> ok 19 - epicsEventWaitWithTimeout(0.015625) delay error 0.004356 sec
> ok 20 - epicsEventWaitWithTimeout(0.007812) delay error 0.012186 sec
> ok 21 - epicsEventWaitWithTimeout(0.003906) delay error 0.016094 sec
> ok 22 - epicsEventWaitWithTimeout(0.001953) delay error 0.018049 sec
> ok 23 - epicsEventWaitWithTimeout(0.000977) delay error 0.019059 sec
> ok 24 - epicsEventWaitWithTimeout(0.000488) delay error 0.019513 sec
> ok 25 - epicsEventWaitWithTimeout(0.000244) delay error 0.019704 sec
> ok 26 - epicsEventWaitWithTimeout(0.000122) delay error 0.019877 sec
> ok 27 - epicsEventWaitWithTimeout(0.000061) delay error 0.019941 sec
> ok 28 - epicsEventWaitWithTimeout(0.000031) delay error 0.019964 sec
> ok 29 - epicsEventWaitWithTimeout(0.000015) delay error 0.019999 sec
> ok 30 - epicsEventWaitWithTimeout(0.000008) delay error 0.019991 sec
> ok 31 - epicsEventWaitWithTimeout(0.000004) delay error 0.019996 sec
> ok 32 - epicsEventWaitWithTimeout(0.000002) delay error 0.019988 sec
> ok 33 - Mean delay error was 0.013227 sec
>
- Andrew
--
Complexity comes for free, simplicity you have to work for.
- Replies:
- RE: Timeouts returning early, was: Build failed in Jenkins Mark Rivers via Core-talk
- References:
- Build failed in Jenkins: epics-base-7.0-win64-test #147 APS Jenkins via Core-talk
- Navigate by Date:
- Prev:
Jenkins build became unstable: epics-base-7.0-win64s-test #143 APS Jenkins via Core-talk
- Next:
RE: Timeouts returning early, was: Build failed in Jenkins Mark Rivers via Core-talk
- 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-7.0-win64-test #147 APS Jenkins via Core-talk
- Next:
RE: Timeouts returning early, was: Build failed in Jenkins Mark Rivers via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
<2020>
2021
2022
2023
2024
| 
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·