Hi Dirk,
On 11/02/2018 05:01 AM, Dirk Zimoch wrote:
It seems I have a hanging test in 3.15 as well
make[3]: Entering directory
`/jenkins/workspace/EPICS-3.15/src/ioc/db/test/O.RHEL7-x86_64'
perl -CSD -MTest::Harness -e 'runtests @ARGV if @ARGV;' dbShutdownTest.t
dbPutLinkTest.t dbLockTest.t testdbConvert.t callbackTest.t
callbackParallelTest.t dbStateTest.t dbCaStatsTest.t scanIoTest.t
dbChannelTest.t dbChArrTest.t chfPluginTest.t arrShorthandTest.t
recGblCheckDeadbandTest.t testPutGetTest.t
dbShutdownTest.t ........... ok
dbPutLinkTest.t ............ ok
dbLockTest.t ............... ok
testdbConvert.t ............ ok
callbackTest.t ............. ok
callbackParallelTest.t ..... ok
dbStateTest.t .............. ok
dbCaStatsTest.t ............ ok
Starting iocInit
iocRun: All initialization complete
Starting iocInit
iocRun: All initialization complete
[Hangs here]
That's scanIoTest, which has had problems on various architectures and
was completely rewritten by Michael for the 3.16 branch in 2015. His
3.16 version probably won't back-port easily to 3.15 though, it uses
some 3.16-only infrastructure IIRC. If it's causing problems you might
want to just disable that test; I'm not sure what else to recommend.
If I am running the tests for different EPICS versions on the same
Jenkins server, can they destructively interfere if the tests happen to
run at the same time? In that case I better change the Jenkins
configuration to use only 1 worker.
They shouldn't do, although you might want to set EPICS_CA_ADDR_LIST to
localhost and EPICS_CA_AUTO_ADDR_LIST to NO just in case. I usually run
the tests in parallel (make -j4 tapfiles) with no problems, but I'm not
running tests on multiple host-arch's on the same CPU.
- Andrew