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

RESOLVED WORKSFORME

Status

Release Engineering
General
--
major
RESOLVED WORKSFORME
5 years ago
2 months ago

People

(Reporter: hwine, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
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.
(Reporter)

Comment 2

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

Updated

5 years ago
Status: NEW → RESOLVED
Last Resolved: 5 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 → ---
(Assignee)

Updated

5 years ago
Product: mozilla.org → Release Engineering
I think we waited long enough?
Status: REOPENED → RESOLVED
Last Resolved: 5 years ago4 years ago
Resolution: --- → WORKSFORME
(Assignee)

Updated

2 months ago
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.