fix rare faulty TEnv initialization when workdir=homedir in two Egamma packages
This implements in Egamma packages, after some delay, a suggested fix from @gstark, who found out that absolute paths (supplied by the PathResolver) are not processed by the TEnv constructor when the executable (athena / analysis framework / ...) runs directly from the home directory. Thank you!
As proposed, the updated code will instead rely upon TEnv::ReadFile(), which should work in all cases. The return code is not checked because neither was it in the TEnv constructor, so this should mimic current behaviour.
I'm adding the relevant labels to tentatively update 21.3 and 21.9 as well. For master, let's discuss separately, @turra having some interest in replacing TEnv altogether.
Merge request reports
Activity
added Analysis Egamma Tools alsoTargeting:21.3 alsoTargeting:21.9 bugfix labels
added 21.2 Derivation analysis-review-required review-pending-level-1 labels
✅ CI Result SUCCESS (hash fbbbdc60)AthDerivation externals ✅ cmake ✅ make ✅ required tests ✅ optional tests ✅ Full details available on this CI monitor view
✅ AthDerivation: number of compilation errors 0, warnings 0
📝 For experts only: Jenkins output [CI-MERGE-REQUEST-GCC62-CC7 909]✅ CI Result SUCCESS (hash fbbbdc60)AnalysisBase AthAnalysis externals ✅ ✅ cmake ✅ ✅ make ✅ ✅ required tests ✅ ✅ optional tests ✅ ✅ Full details available on this CI monitor view
✅ AnalysisBase: number of compilation errors 0, warnings 0
✅ AthAnalysis: number of compilation errors 0, warnings 0
📝 For experts only: Jenkins output [CI-MERGE-REQUEST-CC7 35185]added review-approved label and removed review-pending-level-1 label
mentioned in commit d538147a
added sweep:done label
added sweep:failed label
mentioned in merge request !44450 (merged)