PyJobTransforms: use default asetup for sub-steps running in different release
When running a sub-step (e.g. RDOtoRDOTrigger) in a different release, use the asetup
alias (defined by setupATLAS
) to setup the release instead of the $AtlasSetup
from the user environment. The latter may point to the beta version on afs that is not accessible from within the container.
For my environment, this changes the setup.RDOtoRDOTrigger.sh
file from
source /afs/cern.ch/atlas/software/dist/beta/AtlasSetup/scripts/asetup.sh Athena,21.0,latest
to
asetup Athena,21.0,latest
cc @okuprash
Follow-up fix: !71430 (merged)
Merge request reports
Activity
added full-unit-tests label
added 1 commit
- ebfe7102 - PyJobTransforms: use default asetup in sub-steps running in different release
added Tools main review-pending-level-1 labels
CI Result SUCCESS (hash ebfe7102)Athena AthSimulation AthGeneration externals cmake make tests Full details available on this CI monitor view. Check the JIRA CI status board for known problems
Athena: number of compilation errors 0, warnings 0
AthSimulation: number of compilation errors 0, warnings 0
AthGeneration: number of compilation errors 0, warnings 0
For experts only: Jenkins output [CI-MERGE-REQUEST-EL9 9506] (remote access info)- Resolved by Tadej Novak
Will this work on all sites?
removed review-pending-level-1 label
added review-approved label
mentioned in commit 34d091a7
mentioned in merge request !71430 (merged)