{{cntl.metadata.ProjectName}} Submit Queue Status

E2E Tests Are Troubled But Not Failing

E2E Tests Failing. Entire submit queue blocked. Last merge .

Pull Requests ({{cntl.prsCount}})

{{item.display}} No matches found for "{{cntl.prDisplayValue}}".

#{{pr.Number}}: {{pr.Title}}


{{pr.Time | date:'medium'}} (+{{pr.Additions}}/-{{pr.Deletions}})

Queued For Retest And Merge ({{cntl.e2equeue.length}})

Estimated Merging {{cntl.sqStats.MergeRate}} PRs per day.

#{{pr.Number}}: {{pr.Title}} (+{{pr.Additions}}/-{{pr.Deletions}})


QUEUE {{pr.Login}}

#{{pr.Number}}: {{pr.Title}} (+{{pr.Additions}}/-{{pr.Deletions}})


Historic Merge Bot Decisions

{{item.display}} No matches found for "{{cntl.historyDisplayValue}}".

#{{pr.Number}}: {{pr.Title}}


{{pr.Time | date:'medium'}}

E2E Tests

End-to-End Results

Queue-Blocking Builds

{{$chip.state}} {{$chip.name}} {{$chip.msg}} {{$chip.stability}}

Non-Queue-Blocking Builds

{{$chip.state}} {{$chip.name}} {{$chip.msg}}

Overall Health: {{ cntl.OverallHealth }}

Health percents are the fraction of the time that a given job is stable for the last day, or since the submit queue restarted ({{ cntl.sqStats.StartTime | date:'medium'}}), whichever is shorter. The 24-Hour Test Report shows more detail, along with a list of flaky and broken tests in merge-blocking jobs.

How PRs get ordered in the queue

Requirements for a PR to get automatically merged

Statistics About the Bot

Bot Started: {{ cntl.sqStats.StartTime | date:'medium' }}

Next Sync Loop: {{ cntl.botStats.NextLoopTime | date:'medium' }}

API Calls Per Second: {{ cntl.botStats.APIPerSec }}

Github Rate Limit Count: {{ cntl.botStats.LimitRemaining }}

Github Rate Limit Next Reset: {{ cntl.botStats.LimitResetTime | date:'medium' }}

Retests avoided because of e2e test flakes: {{ cntl.sqStats.RetestsAvoided }}

Flakes ignored: {{ cntl.sqStats.FlakesIgnored }}

API Calls During Last Loop

{{stat.$key}} {{stat.Count}} {{stat.CachedCount}} {{stat.UncachedCount}}

Health chart for the past week

Communicating with the Bot

Github contributors and reviewers can communicate with the mungebot by commenting on a PR with the following commands entered alone in the text field. All commands require the following syntax:

/Command [Optional Args].

Note the forward slashing preceding the command name.

List of Commands

  1. lgtm: applies the lgtm label
  2. lgtm cancel: removes a previously applied lgtm label
  3. approve: approve all the files for which you are an approver
  4. approve cancel: removes your approval on this pull-request