Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • athena athena
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Jira
    • Jira
  • Merge requests 184
    • Merge requests 184
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Issue
    • Repository
  • Activity
  • Graph
  • Commits
Collapse sidebar
  • atlas
  • athenaathena
  • Merge requests
  • !48170

Closed
Created Nov 11, 2021 by Goetz Gaycken@goetzDeveloper
  • Report abuse
Report abuse

Draft: Check for invalid number of data words in pixel ROB fragments.

  • Overview 2
  • Commits 3
  • Pipelines 1
  • Changes 2

Under certain circumstance the number of rod data words is reported incorrectly for some ROB fragments. Such fragments have a suspiciously large number of rod data words and do not pass the ROD fragment validation. They do not contain any data. These fragments are now rejected and treated as TruncatedROB errors.

Fixes segmentation fault discussed in ATLASRECTS-6624.

Edited Nov 11, 2021 by Goetz Gaycken
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: ATLASRECTS-6624_22.0-mc20_handle_fragments_with_invalid_ndata