EPICS Home

Experimental Physics and Industrial Control System


 
2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <2018>  2019  2020  2021  2022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <2018>  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>
Subject: Re: Problem with performstruct test
From: Michael Davidsaver <[email protected]>
To: "Johnson, Andrew N." <[email protected]>, "[email protected]" <[email protected]>
Date: Wed, 19 Sep 2018 13:42:56 -0700 
On 09/19/2018 11:42 AM, Johnson, Andrew N. wrote:
> 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?

Perhaps originally, though it may have been Matej not knowing about TESTPROD.
I find myself wanting to skip installing test* and *Example

> $ ls -1 bin/linux-x86_64
> eget
> pipelineServiceExample
> pvget
> pvinfo
> pvlist
> pvput
> rpcClientExample
> rpcServiceAsyncExample
> rpcServiceExample
> rpcWildServiceExample
> testGetPerformance
> testMonitorPerformance
> testServer
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
Re: Problem with performstruct test Johnson, Andrew N.
Navigate by Date:
Prev: Re: Problem with performstruct test Johnson, Andrew N.
Next: Build failed in Jenkins: epics-7.0 » mac #64 APS Jenkins
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 Johnson, Andrew N.
Next: PSI Jenkins Dirk Zimoch
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <2018>  2019  2020  2021  2022  2023  2024