Jobs which have only MCDecayTreeTuples as output are marked as succeeded
When running jobs with CharmWGProd for Lb2Lll analyses, we ran into a issue that was not caught by the pipeline. A job running over a MC tuple could produce only one or multiple MCDecayTreeTuple(s) but still be marked as finished successfully. We would propose to include a check that an MCDecayTreeTuple and a regular DecayTreeTuple are at least present in order to mark a job over MC as successful.
-
Warn when at least one DecayTree
and oneMCDecayTree
(MC only) isn't present in output following a locallb-ap test ...
. -
Warn when at least one DecayTree
and oneMCDecayTree
(MC only) isn't present in output following a GitLab CI test.