Closed
Bug 1043415
Opened 11 years ago
Closed 11 years ago
Explicitly list gaia-try's priority rather than relying on the fallback
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: emorley, Assigned: emorley)
Details
Attachments
(1 file)
|
1.01 KB,
patch
|
catlee
:
review+
|
Details | Diff | Splinter Review |
gaia-try doesn't appear in the repo priority list in master_common.py, so is given the default priority of "4". This is easy to overlook when reading the config, so lets set it to 4 explicitly.
|
Assignee | |
Comment 1•11 years ago
|
||
Unlisted branches are prioritized at level '4', *so this patch is a no-op*, but
makes it more obvious at what priority gaia-try is currently being treated.
In the future bug 1035304 will adjust this priority, but for now we're leaving it at 4.
Attachment #8461584 -
Flags: review?(catlee)
|
|
||
Updated•11 years ago
|
Attachment #8461584 -
Flags: review?(catlee) → review+
|
|
Assignee | |
Comment 2•11 years ago
|
||
|
||
Comment 3•11 years ago
|
||
something here is now in production
|
|
Assignee | |
Updated•11 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
|
|
||
Comment 4•11 years ago
|
||
something(s) here went to production today
|
||
Updated•7 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•