EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021  2022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: hanging test in 3.15
From: "Johnson, Andrew N. via Core-talk" <[email protected]>
To: "[email protected]" <[email protected]>
Date: Fri, 2 Nov 2018 16:43:34 +0000
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

-- 
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of
speech because I have nothing to say." -- Edward Snowdon

Replies:
Re: hanging test in 3.15 Dirk Zimoch
References:
R7.0.2-rc1 tagged and published at APS Johnson, Andrew N. via Core-talk
Re: R7.0.2-rc1 tagged and published at APS Dirk Zimoch

Navigate by Date:
Prev: Problem with cross-tests Dirk Zimoch
Next: RTEMS5 with epics-base Heinz Junkes
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: R7.0.2-rc1 tagged and published at APS Dirk Zimoch
Next: Re: hanging test in 3.15 Dirk Zimoch
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021  2022  2023  2024 
ANJ, 08 Nov 2018 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·