PhysicsAnalysis: disable post-processing for unit tests

Explicitly disable post-processing for unit tests that do not need it (as discussed at !48559 (comment 5037362)). Also remove 300s TIMEOUT as that is the default in the nightly builds.

This merge request affects 11 packages:

• PhysicsAnalysis/Algorithms/EgammaAnalysisAlgorithms
• PhysicsAnalysis/Algorithms/FTagAnalysisAlgorithms
• PhysicsAnalysis/Algorithms/JetAnalysisAlgorithms
• PhysicsAnalysis/Algorithms/MetAnalysisAlgorithms
• PhysicsAnalysis/Algorithms/MuonAnalysisAlgorithms
• PhysicsAnalysis/Algorithms/SelectionHelpers
• PhysicsAnalysis/Algorithms/TriggerAnalysisAlgorithms
• PhysicsAnalysis/CommonTools/ExpressionEvaluation
• PhysicsAnalysis/D3PDMaker/D3PDMakerCoreComps
• PhysicsAnalysis/MuonID/MuonSelectorTools
• PhysicsAnalysis/TauID/TauAnalysisTools

Affected files list will not be printed in this case

Adding @stavrop ,@krumnack ,@tadej ,@pagessin ,@jojungge as watchers

added Analysis Egamma JetEtmiss Tau Trigger analysis-review-required master review-pending-level-1 labels

added analysis-review-approved label and removed analysis-review-required label

CI Result SUCCESS (hash 12bcd0e5)

	Athena	AthSimulation	AthGeneration	AnalysisBase	AthAnalysis	DetCommon
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
AthGeneration: number of compilation errors 0, warnings 0
AnalysisBase: number of compilation errors 0, warnings 0
AthAnalysis: number of compilation errors 0, warnings 0
DetCommon: number of compilation errors 0, warnings 0
For experts only: Jenkins output [CI-MERGE-REQUEST-CC7 43223]

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

mentioned in commit 6eafd554

merged

added sweep:ignore label

Hi, @fwinkl

This caught me a bit off guard, as I tend to use a reference file when testing things locally when I do development on MuonSelectorTools. I found this to be a convenient way to get the rigor of keeping track of every output change without a need to update some "central" reference file all the time. If this is not a supported/recommended way of working, would you then suggest that I add a reference file? If so, are there instructions somewhere how to do that? (Depending on the size of the ASG_TEST_FILE, the reference file can be a bit large and should probably not be checked into git, but accessed from cvmfs or such.)

As a side note, the fact that I was not automatically tagged on this MR probably means that I am not formally assigned to MuonSelectorTools on GitLab, in spite of my role as working points subgroup convener. If possible, maybe @yoyamagu could be assigned to the package, as he is taking over as subgroup convener in the new year? Who can take care of that?

Cheers, Magnar

@mkbugge, right, if the reference files are too big they should be kept on cvmfs. I realize we didn't have any documentation on that. So I just added some here: https://atlassoftwaredocs.web.cern.ch/guides/cmake/#test-reference-files

If you want to be tagged for changes in a package, you need to add yourself to the watch list.

OK, thanks! I will probably discuss this with @yoyamagu and leave the final decision to him, as he will be the one taking care of the code in the future.