Closed Bug 872021 Opened 11 years ago Closed 10 years ago

update self serve to not allow win64 jobs on m-i

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: hwine, Unassigned)

Details

Pending jobs appears to show 3 m-i win64 jobs as not started for over 24 hours:
 Pending compile(s) @ May 14 07:43:02
win64 (3)
    3 mozilla-inbound
The bug is not that they are pending, it's that they exist - we don't do win64 on inbound anymore, but they still get triggered by self-serve.
/me thanks :philor and goes to brew coffee
Summary: m-i win64 jobs "stuck" in pending → update self serve to not allow win64 jobs on m-i
Still a problem?
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Currently two pending PGOs, from 11 days ago and 1 day ago, so yeah, still a problem; the "go two weeks without triggering (PGO|nightlies) and then self-serve will forget about the jobs that no longer exist" solution just isn't going to work for inbound.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Product: mozilla.org → Release Engineering
I think we waited long enough?
Status: REOPENED → RESOLVED
Closed: 11 years ago → 10 years ago
Resolution: --- → WORKSFORME
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.