On 7/17/19 4:27 PM, APS Jenkins via Core-talk wrote:
See <https://jenkins.aps.anl.gov/job/epics-base-3.15-win64-test/235/display/redirect>
------------------------------------------
macLibTest.tap ............... ok
taskwdTest.tap ...............
Failed 1/8 subtests
blockingSockTest.tap ......... ok
epicsMessageQueueTest.tap .... ok
epicsStackTraceTest.tap ...... ok
ipAddrToAsciiTest.tap ........
not ok 2 - cb.done
Failed 1/5 subtests
osiSockTest.tap .............. ok
Test Summary Report
-------------------
epicsMathTest.tap (Wstat: 0 Tests: 35 Failed: 0)
TODO passed: 8-9, 11-12, 22-23
taskwdTest.tap (Wstat: 0 Tests: 7 Failed: 0)
Parse errors: Bad plan. You planned 8 tests but ran 7.
ipAddrToAsciiTest.tap (Wstat: 0 Tests: 5 Failed: 1)
Failed test: 2
Files=39, Tests=2899, 5 wallclock secs ( 0.80 usr + 0.73 sys = 1.53 CPU)
Result: FAIL
I just ran the above test programs (those same Jenkins-built binaries on the Jenkins build agent machine) by hand, both direct and through the .t wrapper. They, and the ones that failed earlier, all passed for me, so this appears to be a Jenkins wierdism.
I just reverted the other retry in the msi.plt script so this branch will build again shortly. Our Jenkins installation should be getting upgraded tomorrow morning as well, which will restart the build agents. If that doesn't fix the random failures I'll try
rebooting the Windows VM tomorrow.
- Andrew
--
Complexity comes for free, Simplicity you have to work for.
|
