Skip to main content

See which checks ran on a task's pull request

When a project uses the merge lane, the lane tests each task's pull request before it merges. The task's page shows the newest batch of checks that carried that pull request: one row per check, its result, and how long it took. Read it to see why a change is still waiting, or which check stopped it.

Who can do this: anyone who can view the task. Merge gates shows only for a task that opened a pull request in a project with the merge lane, once a batch has tested it. See Use the merge lane for which plans include the lane.

  1. On the task board, select the task's title. Its page opens beside the board.

  2. Select the Details tab, then Summary.

  3. Scroll to Merge gates. Each row names a check, then its result:

    • Passed, or Passed on attempt 2 when it needed a retry.
    • Failed, or Failed (advisory) for a check the merge doesn't wait on.
    • Timed out, Running or Waiting.
    • Skipped: an earlier required check failed, so this one didn't run.
    • Off: the check is switched off for the project.

    A batch with only one check shows on a single line: the check's name, then its result.

  4. Read the text beside a result. It is the check's own report, such as the names of failing tests. Under it is how long the check took, such as 41 min.

  5. Select Open beside a check, where there is one, to read its full log where it ran.

  6. If Merge-lane stages shows below, read each lane run's card: the pull requests it tested, how long each stage took, and Failed or Flaked (passed on a retry) beside a stage that went wrong. It needs Production QA on your organization's plan.

  7. Select Lane run # and its number on a card to open the lane's own run as a task.

The block shows the newest batch only. When the lane tests the pull request again, the rows change to the new results.

Spot a slow lane run on the board​

Each lane run is a task of its own. On the board, its row carries a short figure beside its name, such as 9 gates · 72m: how many checks the run ran and how long it has taken so far. Hover it for Gates this run ran · its wall time. A Slow mark beside it means the run has taken more than twice as long as the last full run of every check. A slow run holds up every pull request behind it in the lane.