Re: Build failed in Jenkins: epics-base-3.15-win32s-test #108

[Michael Davidsaver <mdavidsaver@gmail.com>]

On 04/24/2017 12:34 PM, APS Jenkins wrote:
> src/std/filters/test/O.win32-x86-static/arrTest.tap ............. ok
> src/std/filters/test/O.win32-x86-static/dbndTest.tap ............ 
> Failed 43/59 subtests 
> src/std/filters/test/O.win32-x86-static/syncTest.tap ............ ok
> src/std/filters/test/O.win32-x86-static/tsTest.tap .............. ok
> src/std/rec/test/O.win32-x86-static/analogMonitorTest.tap ....... ok
> src/std/rec/test/O.win32-x86-static/arrayOpTest.tap ............. ok
> src/std/rec/test/O.win32-x86-static/regressTest.tap ............. ok
> 
> Test Summary Report
> -------------------
> src/std/filters/test/O.win32-x86-static/dbndTest.tap          (Wstat: 0 Tests: 16 Failed: 0)
>   Parse errors: Bad plan.  You planned 59 tests but ran 16.
> Files=72, Tests=8578,  6 wallclock secs ( 0.97 usr  0.48 sys +  0.35 cusr  3.57 csys =  5.37 CPU)
> Result: FAIL
> Build step 'Execute shell' marked build as failure

Running dbndTest through valgrind throws up a lot of invalid read
errors.  These are presumably causing crashes in some cases.  Seems to
be related to record field access.