Closed
Bug 1071313
Opened 10 years ago
Closed 10 years ago
talos_from_code.py should allow custom .zips from ash project, throw a sensible error when talos.zip comes from bad location
Categories
(Release Engineering :: Applications: MozharnessCore, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: wlach, Assigned: wlach)
Details
Attachments
(1 file)
1.60 KB,
patch
|
kmoir
:
review+
|
Details | Diff | Splinter Review |
It would be handy to allow custom talos .zips (for Android testing) from the ash branch. Also, the error we currently print when downloading a resource from an invalid location when running on an unsupported branch (e.g. ash currently, mozilla-central) triggers a python exception.
Assignee | ||
Comment 1•10 years ago
|
||
Attachment #8493429 -
Flags: review?(kmoir)
Comment 2•10 years ago
|
||
If this now allows custom zips on ash, would you mind updating the docs at https://wiki.mozilla.org/Buildbot/Talos/Running#Testing_on_Try_Server that jmaher created recently in bug 1054211? :-)
Updated•10 years ago
|
Status: NEW → ASSIGNED
Updated•10 years ago
|
Attachment #8493429 -
Flags: review?(kmoir) → review+
Assignee | ||
Comment 3•10 years ago
|
||
(In reply to Ed Morley [:edmorley] from comment #2) > If this now allows custom zips on ash, would you mind updating the docs at > https://wiki.mozilla.org/Buildbot/Talos/Running#Testing_on_Try_Server that > jmaher created recently in bug 1054211? :-) .zips from foreign locations being disallowed isn't really covered in this documentation. I honestly don't think it's worth mentioning there, as I think it's just unnecessary information that's going to confuse people. Almost no one tests talos .zip's (it's an Android only thing) and it's a given that works on try branches.
Assignee | ||
Comment 4•10 years ago
|
||
Inbound: https://hg.mozilla.org/integration/mozilla-inbound/rev/f294836b305b
Comment 5•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/f294836b305b
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•