Skip to content

HltEventLoopMgr: Use forced run number / time stamp in EventID

Rafal Bielski requested to merge rbielski/athena:hlt-override-timestamp into master

The point of forcing run number / SOR time was to use the right conditions when running at P1 with preloaded data. Right now, we create the correct conditions objects, but for timestamp-based conditions, the ReadCondHandles still expect ones valid for time specified in EventID. This leads to a stall as the inputs with the (wrongly) expected time are not available. The easiest solution is to override the timestamp (and run number for consistency) also in the EventID. Closes ATR-20249.

Tested with:

athenaHLT.py -C "from AthenaCommon.AppMgr import ServiceMgr as svcMgr; svcMgr.HltEventLoopMgr.forceRunNumber=327265; svcMgr.HltEventLoopMgr.forceStartOfRunTime=1497890693000000000;" -n 20 -f /cvmfs/atlas-nightlies.cern.ch/repo/data/data-art/TrigP1Test/data18_13TeV.00360026.physics_EnhancedBias.merge.RAW._lb0151._SFO-1._0001.1 TrigUpgradeTest/full_menu.py

Merge request reports