Update scripts to be compatible with FairSoft jan24

With the version contained in FairSoft jan24 ROOT needs to access some header files from the FairSoft installation, so add the $SIMPATH/include to the list of additional include directories.

added BugFix Build System CI/CD Framework labels

requested review from @p.-a.loizeau

assigned to @p.-a.loizeau

Should we start adding a runner with jan24? maybe in "allowed to fail" mode, but to at least get an overview of the current state?

Not yet. I haven't installed the FairSoft/FairRoot versions for Debian10 and Debian11 on CVMFS. I am still waiting for a patch release since there are some minor issues which I worked around manually for the tests. With my private installation I already found some issues with CbmRoot which I want to fix before announcing the new FairSoft/FairRoot versions.

added 137 commits

• 96e0ccdd...39c00e70 - 136 commits from branch computing:master
• c5d21b4a - Update scripts to be compatible with FairSoft jan24

Compare with previous version

@f.uhlig the two jobs which fail both seem to have some problems with VC. The strange thing is that it is neither the FairSoft version alone or the OS alone, but the combination of the two:

• centOS7 apr21 = OK
• centOS7 nov22 = FAILING
• vae23 apr21 = OK
• vae23 nov22 = FAILING
• debian12 nov22 = OK

The trace is in all cases looking similar to this one for centos7 + nov22p1:

In file included from libL1 dictionary payload:135:
In file included from /tmp/custom-executor49315391/builds/computing/cbmroot/reco/L1/CbmL1Util.h:8:
In file included from /tmp/custom-executor49315391/builds/computing/cbmroot/algo/ca/core/data/CaTrackParam.h:13:
In file included from /tmp/custom-executor49315391/builds/computing/cbmroot/algo/ca/core/pars/CaConstants.h:12:
In file included from /tmp/custom-executor49315391/builds/computing/cbmroot/algo/ca/core/utils/CaSimd.h:7:
/tmp/custom-executor49315391/builds/computing/cbmroot/algo/ca/core/utils/CaSimdVc.h:7:10: remark: could not acquire lock file for module 'Vc': failed to create unique file /cvmfs/fairsoft.gsi.de/centos7/gcc8/fairsoft/nov22p1/lib/Vc.pcm.lock-88702aba: Read-only file system [-Rmodule-build]
#include "Vc/Vc"
         ^
/tmp/custom-executor49315391/builds/computing/cbmroot/algo/ca/core/utils/CaSimdVc.h:7:10: remark: building module 'Vc' as '/cvmfs/fairsoft.gsi.de/centos7/gcc8/fairsoft/nov22p1/lib/Vc.pcm' [-Rmodule-build]
error: unable to open output file '/cvmfs/fairsoft.gsi.de/centos7/gcc8/fairsoft/nov22p1/lib/Vc.pcm': 'Read-only file system'
/tmp/custom-executor49315391/builds/computing/cbmroot/algo/ca/core/utils/CaSimdVc.h:7:10: remark: finished building module 'Vc' [-Rmodule-build]
/tmp/custom-executor49315391/builds/computing/cbmroot/algo/ca/core/utils/CaSimdVc.h:7:10: fatal error: could not build module 'Vc'
#include "Vc/Vc"

Maybe something with the relative path of the include?

@p.-a.loizeau,

where did you run the containers? Virgo2 or Virgo3?

I did not try to run it on Virgo yet, that was only from the CDASH logs. Did not thought about it but will try it now as we can target a specific test instead of running all.

@f.uhlig I could reproduce it on Virgo2/vae23 with the following script (clones + builds + runs one of the failing test + less the resulting log file):

/lustre/cbm/users/ploizeau/apptainer/build_cbmroot_test_florian_fsJan24.sh

added 98 commits

• c5d21b4a...562ced5d - 97 commits from branch computing:master
• d472d553 - Update scripts to be compatible with FairSoft jan24

Compare with previous version

approved this merge request

enabled an automatic merge when the pipeline for d472d553 succeeds

canceled the automatic merge

Same errors still present with

• vae23-linux-x86_64-gcc8-fairsoft_nov22p1-fairroot_v18.8.0
• centos7-linux-x86_64-gcc8-fairsoft_nov22p1-fairroot_v18.8.0

The MR isn't needed any longer. The issue was fixed with the first patch release of jan24.

closed