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  2018  2019  2020  <20212022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Strange UDP message on VxWorks 6.9
From: "Zimoch Dirk \(PSI\) via Core-talk" <core-talk at aps.anl.gov>
To: "anj at anl.gov" <anj at anl.gov>, "mdavidsaver at gmail.com" <mdavidsaver at gmail.com>
Cc: "core-talk at aps.anl.gov" <core-talk at aps.anl.gov>
Date: Tue, 23 Nov 2021 08:33:51 +0000
Hi Andrew,

Thanks for the clarification. As I had never run the test harnesses before on vxWorks and cannot find documentation on
how to do this, I was a bit lost. My build directory is on AFS which I cannot mount on vxWorks. Only my install
directory is on NFS. FTP is no option either because he IOC is in another network. I will copy the O.* directories then.

Dirk

On Mon, 2021-11-22 at 19:04 +0000, Johnson, Andrew N. wrote:
> 
> On Nov 19, 2021, at 2:26 PM, Michael Davidsaver via Core-talk <core-talk at aps.anl.gov> wrote:
> > On 11/19/21 6:05 AM, Zimoch Dirk (PSI) wrote:
> > > BTW: Some other tests harnesses require dbd files like linkTest.dbd that do not get installed (even though the
> > > *Harness.munch files are installed).
> >  
> > I'll defer this to Andrew.
>  
> Currently the configure/os/CONFIG.Common.vxWorksCommon definitions don’t support building .munch files for TESTPROD
> (or TESTPROD_vxWorks) targets, only for PROD (and hence PROD_vxWorks) targets.
> 
> The VxWorks test harnesses aren't actually intended to be installed — the .dbd files aren’t the only files that the
> test code needs to access. Because of the above limitation though we have to build them as PROD targets, and the files
> get installed because of that. Test programs are intended to be run after doing a cd to the appropriate O.<arch>
> directory which is where ‘make runtests’ and friends run them from for all of the host architectures. In my scripts
> for running the tests on VxWorks I cd to the test build directories, load the .munch files and run the harness
> programs directly and they work fine for me.
> 
> I don’t have time to work on fixing the TESTPROD builds myself and I’m not sure that it’s really worth the effort,
> although I wouldn’t object to it being done.
> 
> - Andrew
> 
> -- 
> Complexity comes for free, simplicity you have to work for.
> 

Replies:
Re: Strange UDP message on VxWorks 6.9 Johnson, Andrew N. via Core-talk
References:
Strange UDP message on VxWorks 6.9 Zimoch Dirk (PSI) via Core-talk
Re: Strange UDP message on VxWorks 6.9 Michael Davidsaver via Core-talk
AW: Strange UDP message on VxWorks 6.9 Zimoch Dirk (PSI) via Core-talk
AW: Strange UDP message on VxWorks 6.9 Zimoch Dirk (PSI) via Core-talk
Re: AW: Strange UDP message on VxWorks 6.9 Michael Davidsaver via Core-talk
Re: Strange UDP message on VxWorks 6.9 Johnson, Andrew N. via Core-talk

Navigate by Date:
Prev: Build failed: EPICS Base 7 base-7.0-448 AppVeyor via Core-talk
Next: Re: Strange UDP message on VxWorks 6.9 Johnson, Andrew N. via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024 
Navigate by Thread:
Prev: Re: Strange UDP message on VxWorks 6.9 Johnson, Andrew N. via Core-talk
Next: Re: Strange UDP message on VxWorks 6.9 Johnson, Andrew N. via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024 
ANJ, 23 Nov 2021 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·