Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • R Rec
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 280
    • Issues 280
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Jira
    • Jira
  • Merge requests 50
    • Merge requests 50
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • LHCbLHCb
  • Rec
  • Issues
  • #197
Closed
Open
Issue created Apr 29, 2021 by Christoph Hasse@chasse🤸🏻Contributor

Occasional test failures of hlt2_reco_calo_selectivematching

I think this test randomly fails every now and then with a single diff:

    (SelectiveBremMatchAlg ref) average chi2 | 64109 | 16728.91 | 0.26094 | 0.40398 | 7.3711e-11 | 17.781
    (SelectiveBremMatchAlg new) average chi2 | 64108 | 16728.96 | 0.26095 | 0.40398 | 7.3711e-11 | 17.781

Take for example the lhcb-master-ref slot, test passed in 1311 and 1313 but failed in 1312.

Could it be that we have a race condition or a use after free in that algorithm?

fyi: @cmarinbe @graven @mveghel

Edited Apr 29, 2021 by Carla Marin Benito
Assignee
Assign to
Time tracking