Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • 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 143
    • Merge requests 143
  • 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
  • !24457

Merged
Created Jun 26, 2019 by Knut Zoch@kzochDeveloper

(Temporarily) turn off trigger navigation thinning in TOPQ4

  • Overview 8
  • Commits 2
  • Pipelines 2
  • Changes 1

This temporarily turns off trigger navigation thinning for TOPQ4 derivations. The thinning was effectively only in place for data derivations anyways (in MC, the thinning defaults to empty trigger chains, thus no thinning), but a bug reported in ATR-19385 is starting to affect analysis timelines. With trigger navigation thinning turned off, this bug can be circumvented.

This change is to be reverted asap and really is only a temporary fix for the problems reported in the above ticket. More details are also being discussed in the derivation JIRA ticket ATLASDPD-1296.

Edited Jun 27, 2019 by Knut Zoch
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: TOPQ4-trigger-thinning