Closed
Bug 786984
Opened 12 years ago
Closed 12 years ago
Thunderbird's MozMill builders don't obey trychooser options
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: standard8, Assigned: standard8)
Details
(Whiteboard: [buildbot][thunderbird][try])
Attachments
(4 files)
2.19 KB,
patch
|
jhopkins
:
review+
standard8
:
checked-in+
|
Details | Diff | Splinter Review |
1.25 KB,
patch
|
jhopkins
:
review+
standard8
:
checked-in+
|
Details | Diff | Splinter Review |
987 bytes,
patch
|
jhopkins
:
review+
standard8
:
checked-in+
|
Details | Diff | Splinter Review |
12.70 KB,
patch
|
rail
:
review+
standard8
:
checked-in+
|
Details | Diff | Splinter Review |
The MozMill tests for Firefox were originally set up with a type of "mozmill-all", however Thunderbird's tests are just "mozmill". Thunderbird and Firefox do have slightly different routines for mozmill tests. I'm not sure if we want to merge those together or extend the options on trychooser (which could potentially confuse folks).
Updated•12 years ago
|
Component: Release Engineering: Automation (General) → Release Engineering: Developer Tools
QA Contact: catlee → hwine
Comment 1•12 years ago
|
||
Probably what would least confuse folks would be to put a "mozmill" in a Thunderbird-specific bit of trychooser, and remove the "mozmill-all" which hasn't actually done anything since February 2011 when it was commented out of configs.
Assignee | ||
Comment 2•12 years ago
|
||
That would seem to be a simple replacement just on the trychooser html. What I don't quite understand is that even putting in "-u none" into the patch arguments, the mozmill tests still get run on try-comm-central.
Assignee | ||
Comment 3•12 years ago
|
||
Actually, now I look at it, "-u none" doesn't affect xpcshell or mozmill tests for try-comm-central... ... and having said that, I now see the code at fault. I'll see if I can put a patch up later, or at least explain the issue.
Assignee | ||
Comment 4•12 years ago
|
||
This shows the basic issue for the unit test builder not respecting the trychooser arguments. In misc.py the dep builders use enable_try in the branch config to work out whether or not to use the try chooser. However the unit test builders don't have that and just rely on the branch being 'try' rather than 'try-comm-central'. I've not tested these patches, although I believe they will work.
Assignee | ||
Comment 5•12 years ago
|
||
Add enable_try to the relevant branches for the unittest suites. I couldn't find a b2g_config.py (like there is for dep builders), so I'm assuming there isn't one atm.
Attachment #656923 -
Flags: review?(jhopkins)
Assignee | ||
Comment 6•12 years ago
|
||
As per philor's suggestion, this changes mozmill-all to mozmill on the trychooser selection page as the Firefox builders aren't using mozmill-all atm.
Attachment #656924 -
Flags: review?(jhopkins)
Updated•12 years ago
|
Attachment #656921 -
Flags: review?(jhopkins) → review+
Updated•12 years ago
|
Attachment #656923 -
Flags: review?(jhopkins) → review+
Updated•12 years ago
|
Attachment #656924 -
Flags: review?(jhopkins) → review+
Assignee | ||
Comment 7•12 years ago
|
||
Comment on attachment 656923 [details] [diff] [review] buildbot-configs patch http://hg.mozilla.org/build/buildbot-configs/rev/ef98a7702a61
Attachment #656923 -
Flags: checked-in+
Assignee | ||
Comment 8•12 years ago
|
||
Comment on attachment 656921 [details] [diff] [review] buildbotcustom patch Checked in: http://hg.mozilla.org/build/buildbotcustom/rev/15cf147265b4
Attachment #656921 -
Flags: checked-in+
Assignee | ||
Comment 9•12 years ago
|
||
Comment on attachment 656924 [details] [diff] [review] Tools patch - patch trychooser for mozmill-all -> mozmill Checked in: http://hg.mozilla.org/build/tools/rev/a52bc9b58615
Attachment #656924 -
Flags: checked-in+
Comment 10•12 years ago
|
||
This made it to production today.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 11•12 years ago
|
||
At the moment, this appears to have stopped tests running on try-comm-central. try is ok though, so I'm now pondering the issue.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 12•12 years ago
|
||
Ok, the problem here is that trychooser has a nice subtle hard-coded 'try' for the branch name when generating the unit test builder names. The platform builders don't use this, which explains why we've not noticed issues on the platform selection side. I've changed the trychooser to accept a buildbotBranch value (slightly different to the "branch" for the unittest scheduler, as I understand that is something more like platform-try-comm-central-debug etc) and pass that through to the chooser to use when generating the builder pretty names. Hopefully that will work. I don't think we need to worry about the "TB " prefix as that is included in the platform name right from in the main configs. I've added a test for the try-comm-central branch, although I can't actually run that on my local machine, but I think it should pass.
Attachment #657816 -
Flags: review?(bhearsum)
Updated•12 years ago
|
Attachment #657816 -
Flags: review?(bhearsum) → review?(rail)
Comment 13•12 years ago
|
||
Comment on attachment 657816 [details] [diff] [review] Fix try-comm-central's broken unit tests lgtm
Attachment #657816 -
Flags: review?(rail) → review+
Assignee | ||
Comment 14•12 years ago
|
||
Comment on attachment 657816 [details] [diff] [review] Fix try-comm-central's broken unit tests http://hg.mozilla.org/build/buildbotcustom/rev/e6d93b6a8359
Attachment #657816 -
Flags: checked-in+
Comment 15•12 years ago
|
||
Updated try syntax chooser. Instructions on how to do so are in here: https://wiki.mozilla.org/ReleaseEngineering/How_To/Update_the_Try_Syntax
Comment 16•12 years ago
|
||
Live on production masters.
Assignee | ||
Comment 17•12 years ago
|
||
Just verified it is now working fine on ThunderbirdTry and choosing xpcshell and/or mozmill works correctly, so we can save builder time properly :-)
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•7 years ago
|
Component: Tools → General
You need to log in
before you can comment on or make changes to this bug.
Description
•