Incorrect number of pending builds reported by TBPL

RESOLVED FIXED

Status

Release Engineering
General
RESOLVED FIXED
7 years ago
4 years ago

People

(Reporter: Away for a while, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
Branch
    pending / running
mozilla-central
    983 / 18
tracemonkey
    331 / 3
mozilla-1.9.2
    0 / 7
mozilla-1.9.1
    0 / 1
places
    0 / 4
jaegermonkey
    0 / 13
try
    0 / 28
Total
    1314 / 74

I believe the number of pending builds should be incorrect.  :-)
Should be, but it isn't. The Tegras were turned off on the 11th, because they weren't actually testing the builds they should have been, so there really are that many pending, at least looked at from one angle. I'm pretty sure those coalesce, so from another angle the correct number is always between 1 and 5 for Android Talos since when they are turned back on they'll just run the 5 for the latest queued up job, but I don't think that's really the way we want builds-running talking to us.

When I talked briefly about it with bhearsum, he suggested that I could file a request for an enhancement to builds-running to allow for filtering out certain conditions, but I couldn't imagine wanting to deal with releng bustage by changing the URL that tbpl fetches to exclude the bogus data.

Of course, the solution we would like would be to have someone stop triggering those jobs until there's something to run them, and have someone clear out the existing jobs that aren't ever going to be run, but I didn't get the impression that option was on the table.
Where by builds-running I mean builds-pending, of course.
It appears to me that this bug is INVALID.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INVALID
I've excluded the Tegra jobs from the pending data used by TBPL,
 http://hg.mozilla.org/build/buildapi/rev/96b7ca1b1868
When they come back we can revert, but in the meantime this has dragged on long enough.
Resolution: INVALID → FIXED
(Assignee)

Updated

4 years ago
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.