Experimental Physics and Industrial Control System
On 09/19/2018 12:56 PM, Michael Davidsaver wrote:
>>> ... There are a few other similar test
>> programs spread around the Base tree which are intended for manual
>> operation only and should not be added to TESTS.
>
> Other than not having "test" in the executable name, I haven't noticed
> any systematic way to distinguish these. (eg. cvtFastPerform in libCom/test)
Having "[Pp]erform" in the executable name implies a performance test,
which is really what I was talking about above:
modules/pvData/testApp/O.linux-x86_64/performstruct
modules/pvAccess/testApp/O.linux-x86_64/testGetPerformance
modules/pvAccess/testApp/O.linux-x86_64/testMonitorPerformance
modules/libcom/test/O.linux-x86_64/epicsThreadPerform
modules/libcom/test/O.linux-x86_64/epicsAtomicPerform
modules/libcom/test/O.linux-x86_64/cvtFastPerform
The two pvAccess programs are actually being installed, is this
intentional/correct?
- 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: Problem with performstruct test Michael Davidsaver
- References:
- Problem with performstruct test Dirk Zimoch
- Re: Problem with performstruct test Dirk Zimoch
- Re: Problem with performstruct test Johnson, Andrew N.
- Re: Problem with performstruct test Michael Davidsaver
- Navigate by Date:
- Prev:
Re: Travis emails? Michael Davidsaver
- Next:
Re: Problem with performstruct test Michael Davidsaver
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
<2018>
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Problem with performstruct test Michael Davidsaver
- Next:
Re: Problem with performstruct test Michael Davidsaver
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
<2018>
2019
2020
2021
2022
2023
2024