Update Flavour Tagging qmtest files

The FT qmtest reference file and job options are adjusted for the new FT package. The nightly FT tests should switch to green with this again.

Ping @erodrigu, @sakar, @mschille. This MR needs to be combined with Analysis!338 (merged) (BTaggingChecker) and Phys!338 (merged) (FT Tuning adjustment).

mentioned in merge request Phys!338 (merged)

mentioned in merge request Analysis!338 (merged)

Tiny suggestion: at some other point it would make sense to test on more recent data. I see the dataset dates from 2012.

Yes I totally agree. This was just to get the tests running again asap :-)

And it's fine in that respect. I just made the comment as contractually obliged, in some sense :D.

• [2018-05-05 00:36] Validation started with lhcb-run2-patches#5
• [2018-05-05 00:42] Validation started with lhcb-moore-test#47
• [2018-05-05 01:22] Validation started with lhcb-2018-patches#203
• [2018-05-06 00:28] Validation started with lhcb-moore-test#48
• [2018-05-06 00:33] Validation started with lhcb-2018-patches#204
• [2018-05-06 00:34] Validation started with lhcb-run2-patches#6
• [2018-05-07 00:26] Validation started with lhcb-2018-patches#205
• [2018-05-07 00:28] Validation started with lhcb-moore-test#49
• [2018-05-07 00:30] Validation started with lhcb-run2-patches#7

I will merge this as soon as DaVinci compiles again. Today I see trouble from the stripping side due to recent changes. CC @cvazquez and @malexand.

@erodrigu No changes were made to 2018-patches from Stripping side since Thursday. In fact, these errors didn't appear on Friday's nightlies but today (https://lhcb-nightlies.cern.ch/nightly/compare/lhcb-2018-patches/203/lhcb-2018-patches/202/). Most of the test errors are caused by this:

from Configurables import TrackSys
ImportError: cannot import name TrackSys

and also because of Tf__PatVeloSpaceTool (Calib and IFT lines are affected):

[WARNING] Submodule StrippingArchive.Stripping34.StrippingCalib.StrippingTrackEffDownMuon raises the exception "cannot import name TrackSys" and will be skipped !
[WARNING] Submodule StrippingArchive.Stripping34.StrippingCalib.StrippingTrackEffVeloMuon raises the exception "cannot import name Tf__PatVeloSpaceTool" and will be skipped !

I think this is happenning because Rec failed to build (CC @cattanem): https://lhcb-nightlies.cern.ch/logs/build/nightly/lhcb-2018-patches/203/x86_64-slc6-gcc62-opt/Rec/

Stripping is full green now: https://lhcb-nightlies.cern.ch/nightly/lhcb-2018-patches/build/204/

Yep. But the test is still failing in the nightlies for DaVinciTests/tagging/test_tag_mc12. It would be good to have it green. Can this be sorted out for tomorrow?

added 1 commit

• b46d4425 - Remove debug-level-depending reference output

Compare with previous version

Apparently a debug line slipped into the reference file. I hope the latest commit will turn everything green now.

Are you sure it's not in fact the replacement DEBUG -> SUCCESS rather than the line being removed completely? It's a matter of comparing the validator with the observed log ...

You’re right, but I thought it might be good to let the test pass independently of the BTagging.OutputLevel used.

Fair point.

Reminder: do not forget about that MR to master, which I asked about in another MR related to this one.

merged

mentioned in commit 4368c509

mentioned in commit eb96eeaf

mentioned in merge request !208 (merged)