TrigInDetValidation: Add new ART test based on TrigValSteering

Adding a prototype TrigInDetValidation test as requested in ATR-21512. The plan is to write a test like test_trigindetvalidation_mu_zmumu_ibl_pu40.sh but based on TrigValSteering and standard production transforms (Reco_tf) instead of custom job options. Here only the basic RDO->AOD transform is added with trigger step limited to only two HLT chains. Work on this test will be continued in future MRs.

Tested by submitting with art.py grid as described in the ART User Manual. The job can be seen here:
https://bigpanda.cern.ch/job?pandaid=4759159024

added 693 commits

• e1fbe4bc...05db715a - 692 commits from branch atlas:master
• 3eea7295 - First prototype of new TIDV test

Compare with previous version

added 1 commit

• 4b48a477 - First prototype of new TIDV test

Compare with previous version

changed the description

changed the description

unmarked as a Work In Progress

This merge request affects 2 packages:

• Trigger/TrigValidation/TrigInDetValidation
• Trigger/TrigValidation/TrigValTools

Adding @sutt ,@hartj ,@mvozak ,@jpanduro as watchers

added Trigger master review-pending-level-1 labels

CI Result FAILURE (hash 4b48a477)

	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 15579]

There was a timeout in the DataQuality test (FYI @ponyisi) which is not related to any changes in this MR:

[CI_TEST_WRAPPER] minutes elapsed: 30 
[CI_TEST_WRAPPER] test killed as time quota spent, test warning is issued
ci_test_kill_fam: handling process 13612 ... 

I think that's not a problem for this MR and there's no need to rerun CI.

Hi, yes, in principle the code here is for the IDTrigger ART tests, and as such none of the "required" CI tests should be running this code or, even be affected by them, so any of the failures in the "Required tests" should be completely unrelated.

Cheers Mark

Unit tests are definitely relevant and should be checked. They are all successful, so it's fine.

This MR has also (trivial, but still) a change in TrigValTools in code which is used to steer CI tests for Trigger, so I wouldn't say tests should not run or be completely disregarded.

Anyway, this particular issue is just an unrelated glitch.

OK sorry, I forgot that there were changes in the TrigValTools package. If it were just changes in the TrigInDetValidation then my comment would have been correct, but not with the changes to other packages.

Cheers Mark

added review-approved label and removed review-pending-level-1 label

Code changes look fine.

Magdalena (L1 shifter)

merged

mentioned in commit 450d418a

added sweep:ignore label