cmssw: Empty Trajectory exception in HLT step in many workflows

(At least) 5 workflows fail in the HLT step with exception like below

----- Begin Fatal Exception 30-Sep-2021 12:39:12 CEST-----------------------
An exception of category 'TrackingTools/PatternTools' occurred while
   [0] Processing  Event run: 1 lumi: 60 event: 2951 stream: 1
   [1] Running path 'HLT_DoubleTrkMu_16_6_NoFiltersNoVtx_v1'
   [2] Calling method for module CkfTrackCandidateMaker/'hltIterL3OITrackCandidatesNoVtx'
Exception Message:
Trajectory::check() - information requested from empty Trajectory 
----- End Fatal Exception -------------------------------------------------
  • 11630.0: path HLT_DoubleTrkMu_16_6_NoFiltersNoVtx_v1 module HLT_DoubleTrkMu_16_6_NoFiltersNoVtx_v1 (log)
  • 11650.911 path HLT_DoubleTrkMu_16_6_NoFiltersNoVtx_v1 module hltIterL3OITrackCandidatesNoVtx (log)
  • 11723.17 path HLT_DoubleTrkMu_16_6_NoFiltersNoVtx_v1 module hltIterL3OITrackCandidatesNoVtx (log)
  • 13034.0 path HLT_TrkMu6NoFiltersNoVtx_v1 module hltIterL3OITrackCandidatesNoVtx (log)
  • 13034.99 path HLT_OldMu100_v3 module hltL3TrackCandidateFromL2OIState (log)

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 16 (16 by maintainers)

Most upvoted comments

PR tests did not catch this bug, plain and simple. Some bugs are only uncovered by IB tests as they involve many more workflows/statistics.

The WFs are taking a long time to run, but I think I will manage to submit the PR by tonight…

@swagata87, in the interest of time, since the fix seems well understood, you could open the PR already, have it reviewed, and have the tests run automatically (incl. the additional wfs), which will be done anyway later.

(But unless any of the experts agrees, please proceed with your current plan.)

I could reproduce the issue in 11630.0, applied a fix in TrackingTools/TrajectoryFiltering/interface/MinHitsTrajectoryFilter.h, and reran 11630.0 w/o any problem this time

I’ll check with other workflows reported here also (11650.911, 11723.17, 13034.0, 13034.99), and if all of them run fine then I will submit a bugfix PR with the fix.

The WFs are taking a long time to run, but I think I will manage to submit the PR by tonight…

Sorry about the problems caused by my earlier PR