Closed
Bug 880506
Opened 11 years ago
Closed 11 years ago
Stop running Jetpack tests (from the Jetpack tree) against anything other than mozilla-central
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: KWierso, Assigned: philor)
References
()
Details
(Whiteboard: [capacity])
Attachments
(1 file)
1.30 KB,
patch
|
armenzg
:
review+
armenzg
:
checked-in+
|
Details | Diff | Splinter Review |
We're going to be landing some changes to Jetpack that will cause tests to fail when run against a version of Firefox older than 24.
I've already hidden all of the non-central builders on the Jetpack tree, but I think we can completely shut off the non-central builders there at this point and just use the in-tree versions of the SDK for tests against beta and aurora.
So basically, only the currently-visible tests at https://tbpl.mozilla.org/?tree=Jetpack (plus the hidden Win64 tests) need to continue running, everything else in the Jetpack tree can be shut down.
Assignee | ||
Updated•11 years ago
|
Component: Release Engineering → Release Engineering: Automation (General)
QA Contact: catlee
Assignee | ||
Comment 1•11 years ago
|
||
I think that would look a little like this, since the "what branches do we run it on for on-push builds?" thing is http://mxr.mozilla.org/build/source/buildbot-configs/mozilla-tests/config.py#1356 with the funny merge comment.
Attachment #759583 -
Flags: review?(catlee)
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → philringnalda
Whiteboard: [capacity]
Comment 2•11 years ago
|
||
Comment on attachment 759583 [details] [diff] [review]
[configs] fix
I will land it.
Attachment #759583 -
Flags: review?(catlee) → review+
Updated•11 years ago
|
Attachment #759583 -
Flags: checked-in+
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•6 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•