Closed
Bug 915481
Opened 11 years ago
Closed 11 years ago
Stop try tegra jobs pending for >6 hours
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Infrastructure & Operations Graveyard
CIDuty
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Callek, Assigned: Callek)
Details
Attachments
(1 file)
(deleted),
image/png
|
Details |
There is currently a tegra pending count of 947 of which ~895 are try.
Currently the oldest is 11 hours old.
We are going to go through and cancel all try tegra jobs that have been pending for > 6 hours to compensate while we work on the systemic problems in Bug 915457 and Bug 915465
Assignee | ||
Comment 1•11 years ago
|
||
To everyone CC'ed with this comment:
You had recently (today greater than 6 hours ago) done a try push with android tegra tests being scheduled. We had had a large backlog of tegra jobs and decided to cancel many of them.
If you truely needed them your best bet is to retrigger the Android 2.2 Build job on your push, and then see #releng and we'll help you force the priority for your job to be higher.
----
For those who care about this bug outside of those whose jobs I canceled:
We are now at 427 pending tegra jobs globally, all of which (afaict) are try.
I will be attaching a graph of pendings per OS for try-only right after this, of which the purple line is tegras.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 2•11 years ago
|
||
Updated•6 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•