I am running the libCom tests on vxWorks to see if I broke anything (implementing new atomicCompareAndSwap). I found that some tests were failing (even crashing) already with the current 7.0 version (commit :1cacd05).
Listing the faults here (full log attached)
Note the crash of "await" in the first test!
(Sometimes it prints instead: (await): Unhandled C++ exception resulted in call to terminate )
It dies taking an uninitialized semaphore.
-> tt
0x00129464 vxTaskEntry +0x48 : epicsThreadEntry ()
0x0066769c epicsThreadEntry+0x80 : <unnamed>::dowait(void *) ()
0x00618098 <unnamed>::dowait(void *)+0x1c : epicsEvent::wait() ()
0x0065f14c epicsEvent::wait()+0x24 : semTake ()
0x001e7738 semTake +0xac : 0x00000004 ()
value = 0 = 0x0
***** epicsThreadTest *****
1..15
# System has 1 CPUs
ok 1 - ncpus > 0
# main() thread 0x50fa10
not ok 2 - Join delayed parent (0 seconds) # TODO Thread join doesn't work
ok 3 - Join tests #1 completed
not ok 4 - Join delayed parent (0 seconds) # TODO Thread join doesn't work
ok 5 - Join tests #2 completed
ok 6 - pget == pset
ok 7 - thread.getPriority() == epicsThreadGetPriority(self)
ok 8 - pget == pset
ok 9 - thread.getPriority() == epicsThreadGetPriority(self)
ok 10 - pget == pset
ok 11 - thread.getPriority() == epicsThreadGe
0xprogram4f9e10
(Eawaitxception curren): t instruction addtask 0xress: 0x4f9e1000000004 has had a
failure and has beeMachine Status Regisn stopped.
ter: 0x0x0004f9e108b032 (
awaCondition Register: it0x): 48000882fatal
kernel task-level Task: exception!0x
4f9e10tPriority(self) "
await"
not ok 12 - infoB.didSomething
ok 13 - threadA epicsThreadIsOkToBlock() = 0
not ok 14 - infoA.didSomething
ok 15 - threadB epicsThreadIsOkToBlock() = 1
Results
=======
Tests: 15
Passed: 13 = 86.67%
Failed: 2 = 13.33%
***** epicsEventTest *****
not ok 15 - epicsEventWaitWithTimeout(0.250000) delay error -0.000001 sec # TODO Known issue with delay calculation
not ok 16 - epicsEventWaitWithTimeout(0.125000) delay error -0.008332 sec # TODO Known issue with delay calculation
not ok 17 - epicsEventWaitWithTimeout(0.062500) delay error -0.012500 sec # TODO Known issue with delay calculation
not ok 18 - epicsEventWaitWithTimeout(0.031250) delay error -0.014586 sec # TODO Known issue with delay calculation
***** epicsSockResolveTest *****
not ok 26 - aToIPAddr("127.0.0.test", 4000) -> 0
# IP=0x7f000000, port=4000
not ok 27 - aToIPAddr("127.0.0.test:42", 4000) -> 0
# IP=0x7f000000, port=42
not ok 30 - aToIPAddr("1.2.3.4.5", 4000) -> 0
# IP=0x1020304, port=4000
not ok 31 - aToIPAddr("1.2.3.4.5:6", 4000) -> 0
# IP=0x1020304, port=6
***** epicsStdlibTest *****
not ok 166 - Double '1e-330' => underflow # TODO Not detected on VxWorks
***** macDefExpandTest *****
# Got "", expected "BAR".
not ok 27 - ${=BAR}
# Got "xy", expected "xBARy".
not ok 28 - x${=BAR}y
After finishing, ("Reached mainExit") the test program hangs instead of returning to the vxWorks shell.
If started from a vxWorks startup script, it ends in a loop. printing over and over again:
->
Shell task 'tShell0' restarted...
Attachment:
R7.0.5-251-g1cacd05.log
Description: R7.0.5-251-g1cacd05.log
- Replies:
- Re: failing tests on vxWorks Johnson, Andrew N. via Core-talk
- Navigate by Date:
- Prev:
Re: Make keeps installing the same files Johnson, Andrew N. via Core-talk
- Next:
[Bug 1932118] Re: Bug in vxWorks epicsAtomicCmpAndSwapIntT Dirk Zimoch 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:
Re: Make keeps installing the same files Johnson, Andrew N. via Core-talk
- Next:
Re: failing tests on vxWorks Johnson, Andrew N. 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
|