Fix mdfdump test

mdfdump.py was failing in the test because of the error

RunStampCheck       ERROR Database not up-to-date. No valid data for run 6718861 at 1970-01-01 00:00:00.0 UTC

and was printing twice the content of the same RawEvent.

The test was passing because, from the reference file, it was expecting the failure (it's not the first time I see this kind of issue).

I noticed the problem because with !3510 (merged) the RunStampCheck is implicitly disabled (it does not make sense in Run3), thus fixing the configuration error in mdfdump.py.

added lhcb-dd4hep label

assigned to @rmatev

added RTA label

• [2022-04-24 00:04] Validation started with lhcb-dd4hep#1102

Thanks for the fix!

and was printing twice the content of the same RawEvent.

this is pretty weird behaviour. Anyway, RunStampCheck is going away...

approved this merge request

added testing label

merged

mentioned in commit a3262396

mentioned in issue Moore#426 (closed)