Closed
Bug 1142088
Opened 10 years ago
Closed 8 years ago
Remove jobs from the runner blacklist (tracking task)
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mrrrgn, Unassigned)
Details
Runner tries to avoid rebooting machines after a job, however, for certain job types this still causes problems. The solution to this was to add a blacklist, so that certain job types still trigger reboots:
45 def get_buildname_blacklist():
46 '''
47 A list of build name expressions which will coerce a halt, names are
48 retrieved from buildapi via get_recent_builds().
49 '''
50 # reboot after android, b2g emulator, reftest, or mochitest jobs
51 return ['.*android.*', '.*emulator.*', '.*mochi.*', '.*reftest.*']
Right now, we seem to reboot after 3/5 jobs on average. To decrease this number, each entry in this blacklist should be tackled, one by one, so that they can be removed form the blacklist.
| Assignee | ||
Updated•8 years ago
|
Component: Tools → General
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•