Re: EPICS 7 build failures on Appveyor/Windows

[Ralph Lange via Core-talk <core-talk@aps.anl.gov>]

On Fri, 20 Sep 2019 at 14:28, Michael Davidsaver <mdavidsaver@gmail.com> wrote:

On Fri, Sep 20, 2019, 4:53 AM Ralph Lange via Core-talk <core-talk@aps.anl.gov> wrote:

So... the winners are

Commit c0a04eae was hanging the mingw builds (build 423)

Commit d5899699 was hanging one of the VS builds (build 454) 

Any hint at where/why these hang?  Why not at APS as well?  Troubleshooting stuck tests in CI is hard enough on Linux.  I have no idea how to start on Windows.

Well, looking at the build log, one thing is a clear failure in modules/libCom/test:

8292epicsStackTraceTest.t ......

8293Failed 1/5 subtests

8294 (less 3 skipped subtests: 1 okay)

8295ipAddrToAsciiTest.t ........ ok

8296osiSockTest.t .............. ok

8297

8298Test Summary Report

8299-------------------

8300epicsStackTraceTest.t (Wstat: 0 Tests: 5 Failed: 1)

8301 Failed test: 5

8302Files=42, Tests=4116, 190 wallclock secs ( 0.19 usr + 0.09 sys = 0.28 CPU)

8303Result: FAIL

8304Failed 1/42 test programs. 1/4116 subtests failed.

and then I see further down

8486mingw32-make -C std/rec runtests

without ever seen make actually descend into that directory. Looks fishy.

Cheers,

~Ralph