Stop try tegra jobs pending for >6 hours

RESOLVED FIXED

Status

RESOLVED FIXED
5 years ago
6 months ago

People

(Reporter: Callek, Assigned: Callek)

Tracking

Details

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
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

5 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
Last Resolved: 5 years ago
Resolution: --- → FIXED
(Assignee)

Comment 2

5 years ago
Created attachment 803458 [details]
graph of pending count today

Updated

6 months ago
Product: Release Engineering → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.