add DerivationFrameworkART package
Merge request reports
Activity
added master label
added Derivation review-pending-level-1 labels
✅ CI Result SUCCESS (hash b5cae13b)Athena AthSimulation AnalysisBase AthGeneration externals ✅ ✅ ✅ ✅ cmake ✅ ✅ ✅ ✅ make ✅ ✅ ✅ ✅ required tests ✅ ✅ ✅ ✅ optional tests ✅ ✅ ✅ ✅ Full details available on this CI monitor view
✅ Athena: number of compilation errors 0, warnings 0
✅ AthSimulation: number of compilation errors 0, warnings 0
✅ AnalysisBase: number of compilation errors 0, warnings 0
✅ AthGeneration: number of compilation errors 0, warnings 0
📝 For experts only: Jenkins output [CI-MERGE-REQUEST-CC7 12569]- Resolved by James Catmore
- Resolved by James Catmore
- Resolved by James Catmore
Since the scripts are generated do they need to be in the repository at all? There is a similar use-case when generating trigger menus. There the menu files are created during compilation. Maybe something to consider. See: https://gitlab.cern.ch/atlas/athena/-/blob/master/Trigger/TriggerCommon/TriggerMenuXML/CMakeLists.txt
added review-pending-level-2 label and removed review-pending-level-1 label
- Resolved by James Catmore
Hi,
I have another, principal comment. do you really need to have like 300 python files, which basically contains the same code ?
I do not think this is efficient at all....
Shoudln't there be one python file, which is called with many different parameters to have a different tests ?
Best, Pavol [as L2 MR shifter]
added review-user-action-required label
added urgent label
added RC Attention Required review-approved labels and removed review-pending-level-2 review-user-action-required labels