Experimental Physics and
Industrial Control System

On 4. June 2017 at 16:50:13, Marty Kraimer ([email protected]) wrote:

I have also spent some time looking at the  epicsMutex::invalidMutex() messages.

Is it possible to rerun your tests with using a version of pvAccessCPP and pvaClientCPP from my git repository?
Thus
git clone https://github.com/mrkraimer/pvaClientCPP.git

 git clone https://github.com/epics-base/normativeTypesCPP.git

 git clone https://github.com/mrkraimer/pvAccessCPP.git

 git clone https://github.com/epics-base/pvCommonCPP.git

 git clone https://github.com/epics-base/pvDataCPP.git

 git clone https://github.com/epics-base/pvDatabaseCPP.git

 git clone https://github.com/epics-base/exampleCPP.git

 git clone https://github.com/epics-base/pvaSrv.git

Marty



On 06/04/2017 09:23 AM, Heinz Junkes wrote:

Hi Folks,

today I played with the the epics 3.16 release on linux-86_64 …

I installed epics base from git-hub.

git clone https://github.com/epics-base/epics-base.git

compile, make runtests … ok

Then the v4 stuff also from git:

 git clone https://github.com/epics-base/pvaClientCPP.git

 git clone https://github.com/epics-base/normativeTypesCPP.git

 git clone https://github.com/epics-base/pvAccessCPP.git

 git clone https://github.com/epics-base/pvCommonCPP.git

 git clone https://github.com/epics-base/pvDataCPP.git

 git clone https://github.com/epics-base/pvDatabaseCPP.git

 git clone https://github.com/epics-base/exampleCPP.git

 git clone https://github.com/epics-base/pvaSrv.git

make runtests in example CPP leads to the follwing error:

...

make[1]: Entering directory '/home/cryvisil/EPICS/V4/exampleCPP/test'

make -C O.linux-x86_64 -f ../Makefile TOP=../.. \

    T_A=linux-x86_64 runtests

make[2]: Entering directory '/home/cryvisil/EPICS/V4/exampleCPP/test/O.linux-x86_64'

perl -CSD -MTest::Harness -e 'runtests @ARGV if @ARGV;' pvaClientTest.t pvaClientTestPutData.t pvaClientTestGetData.t pvaClientTestMonitorData.t pvaClientTestPutGetMonitor.t pvaClientTestPutGet.t

pvaClientTest.t ............... 6/7 terminate called after throwing an instance of 'epicsMutex::invalidMutex'

  what():  epicsMutex::invalidMutex()

pvaClientTest.t ............... Dubious, test returned 134 (wstat 34304, 0x8600)

All 7 subtests passed

pvaClientTestPutData.t ........ 1/38 terminate called after throwing an instance of 'epicsMutex::invalidMutex'

  what():  epicsMutex::invalidMutex()

pvaClientTestPutData.t ........ Dubious, test returned 134 (wstat 34304, 0x8600)

All 38 subtests passed

pvaClientTestGetData.t ........ 1/26 terminate called after throwing an instance of 'epicsMutex::invalidMutex'

  what():  epicsMutex::invalidMutex()

pvaClientTestGetData.t ........ Dubious, test returned 134 (wstat 34304, 0x8600)

All 26 subtests passed

pvaClientTestMonitorData.t .... 1/26 terminate called after throwing an instance of 'epicsMutex::invalidMutex'

  what():  epicsMutex::invalidMutex()

pvaClientTestMonitorData.t .... Dubious, test returned 134 (wstat 34304, 0x8600)

All 26 subtests passed

pvaClientTestPutGetMonitor.t .. 1/19 terminate called after throwing an instance of 'epicsMutex::invalidMutex'

  what():  epicsMutex::invalidMutex()

pvaClientTestPutGetMonitor.t .. Dubious, test returned 134 (wstat 34304, 0x8600)

All 19 subtests passed

pvaClientTestPutGet.t ......... ^C/home/cryvisil/EPICS/base/configure/RULES_BUILD:337: recipe for target 'runtests' failed

make[2]: [runtests] Interrupt (ignored)

/home/cryvisil/EPICS/base/configure/RULES_ARCHS:58: recipe for target 'runtests.linux-x86_64' failed

make[1]: *** [runtests.linux-x86_64] Interrupt

/home/cryvisil/EPICS/base/configure/RULES_DIRS:84: recipe for target 'test.runtests’ failed

...

Test Summary Report

-------------------

pvaClientTest.t             (Wstat: 34304 Tests: 7 Failed: 0)

  Non-zero exit status: 134

pvaClientTestPutData.t      (Wstat: 34304 Tests: 38 Failed: 0)

  Non-zero exit status: 134

pvaClientTestGetData.t      (Wstat: 34304 Tests: 26 Failed: 0)

  Non-zero exit status: 134

pvaClientTestMonitorData.t  (Wstat: 34304 Tests: 26 Failed: 0)

  Non-zero exit status: 134

pvaClientTestPutGetMonitor.t (Wstat: 34304 Tests: 19 Failed: 0)

  Non-zero exit status: 134

pvaClientTestPutGet.t       (Wstat: 34304 Tests: 3 Failed: 0)

  Non-zero exit status: 134

Files=6, Tests=119,  6 wallclock secs ( 0.05 usr  0.00 sys +  0.41 cusr  0.08 csys =  0.54 CPU)

Result: FAIL

Failed 6/6 test programs. 0/119 subtests failed.

Heinz