| 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 <2019> 2020 2021 2022 2023 2024 2025 | 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 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: epicsThreadOnceTest/epicsThreadPriorityTest failures |
| From: | "Johnson, Andrew N. via Core-talk" <[email protected]> |
| To: | "[email protected]" <[email protected]> |
| Date: | Thu, 18 Jul 2019 15:48:14 +0000 |
|
Heinz, These failures were on Windows, and I'm hoping they're transient. We've just upgraded our Jenkins version which has restarted the build agents on that box, and I'm re-running those tests right now. - Andrew On 7/18/19 2:47 AM, Heinz Junkes via Core-talk wrote:
Michael, is this RTEMS related? When I started trying to use RTEMS5 with osd/posix I was confronted with exactly this problem. epicsThreadOnce and epicsThreadPriority issues. I developed a lot of "cramp constructions" to make it work. Then Till had built in a modification for "non-epicsThreads may receive wrong priority and crash” (https://bugs.launchpad.net/epics-base/+bug/1816841) affecting SCHED_FIFO? and my problems with RTEMS were solved with it and I could take away my messed up modifications. Since then I had no stress anymore with that. HeinzOn 17. Jul 2019, at 20:32, Michael Davidsaver via Core-talk <[email protected]> wrote: I can't recall seeing failures in epicsThreadOnceTest or epicsThreadPriorityTest before... On 7/17/19 11:27 AM, APS Jenkins via Core-talk wrote:Test Summary Report ------------------- epicsMathTest.tap (Wstat: 0 Tests: 35 Failed: 0) TODO passed: 8-9, 11-12, 22-23 epicsThreadOnceTest.tap (Wstat: 0 Tests: 11 Failed: 2) Failed tests: 1, 8 epicsThreadPriorityTest.tap (Wstat: 0 Tests: 5 Failed: 1) Failed test: 3 Parse errors: Bad plan. You planned 7 tests but ran 5. ipAddrToAsciiTest.tap (Wstat: 0 Tests: 5 Failed: 1) Failed test: 2 Files=39, Tests=2898, 5 wallclock secs ( 0.61 usr + 0.70 sys = 1.31 CPU) Result: FAIL -- Complexity comes for free, Simplicity you have to work for. |