search

DUNE-DAQ / daq-buildtools

Make life for developers easier through a collection of CMake functions and scripts
0 stars 1 forks source link

Johnfreeman/daq release issue337 shorten install paths #258

Closed jcfreeman2 closed 9 months ago

jcfreeman2 commented 9 months ago

A couple of weeks ago, I shortened the path of our installed packages. Details are in https://github.com/DUNE-DAQ/daq-release/issues/337, but long story short, while previously we had installations in directory structures like:

/cvmfs/dunedaq-development.opensciencegrid.org/nightly/NAFD24-01-01/spack-0.20.0-gcc-12.1.0

now we have them in, e.g.

/cvmfs/dunedaq-development.opensciencegrid.org/nightly/NAFD24-02-08

...i.e., I've dropped the spack-0.20.0-gcc-12.1.0 (which itself had a softlink called default).

The phase space of tests you could in principle run to test this is quite large, but what we want to establish is that the daq-buildtools on this feature branch can work with the new shortened path and be backwards compatible with the earlier, long path. A disadvantage of testing with the new nightlies is that there's in fact a soft link called spack-0.20.0-gcc-12.1.0 which allows our current release of daq-buildtools (v7.5.0) to not choke. However, there's a "fake" frozen release called nddaq-v3.1.5-a9 which contains the short path, and a (real) frozen release called nddaq-v4.3.0-a9 which uses the traditional long one. It would probably suffice just to check that dbt-setup-release and dbt-create work with these two frozen releases.

andrewmogan commented 9 months ago

As instructed, I've tested that dbt-setup-release and dbt-create work with the "fake" and "real" frozen releases. The explicit steps are listed below. Each test was run in a fresh shell on np04-srv-015. All tests started with

cd $WORK_DIR
git clone https://github.com/DUNE-DAQ/daq-buildtools.git -b johnfreeman/daq-release_issue337_shorten_install_paths
source ./daq-buildtools/env.sh

Following this, dbt-setup-release nddaq-v3.1.5-a9 and dbt-setup-release nddaq-v4.3.0-a9 both worked as expected. For the dbt-create tests, following the appropriate dbt-create command,

cd <dbt_created_area>
source env.sh
cd sourcecode
git clone https://github.com/DUNE-DAQ/ndreadoutlibs.git
cd $DBT_AREA_ROOT
dbt-build

Both cases succeeded.