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

Pull Requests ({{cntl.prsCount}})

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

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

{{pr.Reason}}

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

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

Estimated Merging {{cntl.sqStats.MergeRate}} PRs per day.
CURRENTLY RUNNING {{pr.Login}}

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

{{pr.ExtraInfo}}

CURRENTLY RUNNING BATCH
QUEUE {{pr.Login}}

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

{{pr.ExtraInfo}}

Historic Merge Bot Decisions

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

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

{{pr.Reason}}

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

CI

Presubmit Results

Batch Builds

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

Single Builds

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

End-to-End Results

Non-Queue-Blocking Builds

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

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

Authors, reviewers, and owners can communicate with k8s-ci-robot by commenting on a PR with the various commands entered in comments.
Specific syntax is available here.