Closed Bug 754650 Opened 13 years ago Closed 13 years ago

Determine why an Oak Nightly has been pending multiple days

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Platform:
x86_64
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: Callek, Unassigned)

Details

(Whiteboard: [buildduty])

So, I just happened to glance at the Infrastructure report for tonight. We have only 12 builds running, and an [OSX] oak nightly thats been pending for well over a day. https://secure.pub.build.mozilla.org/buildapi/pending?revision=d1691307f1c5 Not sure what is going on here, but needs at least some sort of kick.
I think that's b/c oak uses 10.7 builders for nightlies, but self-serve doesn't know that, so it triggers ALL the nightlies.
(In reply to Chris AtLee [:catlee] from comment #1) > I think that's b/c oak uses 10.7 builders for nightlies, but self-serve > doesn't know that, so it triggers ALL the nightlies. That sounds plausible, and it is no longer listed in pending... I'm RESO/WFM for now.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.