Closed
Bug 857486
Opened 11 years ago
Closed 11 years ago
Still scheduling 'WINNT 6.1 x86-64 mozilla-central pgo-build' but no builder
Categories
(Release Engineering :: Release Automation: Other, defect, P4)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nthomas, Assigned: armenzg)
References
Details
See https://secure.pub.build.mozilla.org/buildapi/pending for the most recent examples, I culled the earlier ones out assuming they were just left overs. There's no builder to do the job.
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → armenzg
Assignee | ||
Comment 1•11 years ago
|
||
14:17 catlee: self-serve doesn't know what builders are enabled 14:17 catlee: so it looks over the past day? week? of builds to figure out what builds to trigger 14:25 catlee: armenzg: you can wait 2 weeks and then delete all the pending jobs 14:25 catlee: or delete 2 weeks of builds prior to today which lead me to write this SQL statement: delete from buildrequests where buildername like 'WINNT 6.1 x86-64%pgo-build' and complete=1 and submitted_at>'1363372336'; Should I execute such command? could there be any consequences? The date is equivalent to this: GMT: Fri, 15 Mar 2013 18:32:16 GMT
Priority: -- → P4
Assignee | ||
Comment 2•11 years ago
|
||
I'm leaving towards leaving it as is and remove in two weeks time.
Flags: needinfo?(nthomas)
Reporter | ||
Comment 3•11 years ago
|
||
Yes, that's fine. I'll probably kill pending jobs every few days just to keep that tidy. I wonder if we can have self-serve poll an information service instead of the db for the set of builders for a task. The info service could get data from some kind of script like builder_list.py and a master instance, updated on merges to production.
Flags: needinfo?(nthomas)
Assignee | ||
Comment 4•11 years ago
|
||
No pending jobs left. Thanks to whoever have been doing the cleanup.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•