Closed
Bug 973900
Opened 11 years ago
Closed 11 years ago
Please schedule desktop jit-tests on all trunk trees and make them ride the trains
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dminor, Assigned: kmoir)
References
(Depends on 1 open bug)
Details
Attachments
(4 files)
|
4.36 KB,
patch
|
rail
:
review+
kmoir
:
checked-in+
|
Details | Diff | Splinter Review |
|
5.90 KB,
text/plain
|
Details | |
|
14.47 KB,
text/plain
|
Details | |
|
8.97 KB,
text/plain
|
Details |
It looks like all of the consistent oranges for the desktop jit-tests on Cedar are now fixed and we're down to intermittents.
It is difficult to tell whether or not we hit more intermittents on the test machines than we do on the build machines while running on Cedar, due to the low volume of pushes.
I think we should turn these on for desktop builds on trunk trees, hidden for now, and see how things look.
We might need to resolve Bug 969986 first.
Comment 1•11 years ago
|
||
And three other unfiled blockers, besides getting all Linux to run on try and include them in trychooser:
* decide whether to run them on all Mac and Windows platforms (probably not)
* some parallel permaorange on 10.6 opt and WinXP opt+debug
* the Linux slaves are so brutally slow that for linux64 asan and debug, this'll tie with the very slowest of browser-chrome runs for being the long pole for completing tests on a push
| Assignee | ||
Updated•11 years ago
|
Assignee: nobody → kmoir
| Assignee | ||
Comment 2•11 years ago
|
||
dminor: Can you address philor's questions in comment #1? Should I indeed enable them on all trunk trees and ride the trains for all platforms or are there some platforms where they should be excluded for now?
Flags: needinfo?(dminor)
| Reporter | ||
Comment 3•11 years ago
|
||
I'm not sure if I'm the right person to decide this. I think the minimum would be to cover platforms that currently run them as part of make check (Linux, Windows XP, Mac OS X 10.8).
I have seen different results on Windows 7 and 8 than on WinXP on Cedar, but I'm not sure if we actually need that additional test coverage.
Ted, Terrence, any preferences here?
Flags: needinfo?(terrence)
Flags: needinfo?(ted)
Flags: needinfo?(dminor)
Comment 4•11 years ago
|
||
Let's schedule them on all platforms for now. If we decide we don't need them we can always selectively disable them later.
Flags: needinfo?(ted)
Comment 5•11 years ago
|
||
(although honestly I'd take philor's advice over mine)
Comment 6•11 years ago
|
||
Please do turn these on everywhere. I expect that this will expose real issues that are currently hidden because we are not already running them on all of our tier-1 platforms. We will fix anything that crops up.
Flags: needinfo?(terrence)
| Assignee | ||
Comment 7•11 years ago
|
||
Will attach builder diffs too
Attachment #8400152 -
Flags: review?
| Assignee | ||
Updated•11 years ago
|
Attachment #8400152 -
Flags: review? → review?(rail)
| Assignee | ||
Comment 8•11 years ago
|
||
| Assignee | ||
Comment 9•11 years ago
|
||
| Assignee | ||
Comment 10•11 years ago
|
||
Comment 11•11 years ago
|
||
Comment on attachment 8400152 [details] [diff] [review]
bug973900.patch
Review of attachment 8400152 [details] [diff] [review]:
-----------------------------------------------------------------
lgtm
::: mozilla-tests/config.py
@@ +1927,5 @@
> + if 'fedora' in slave_platform:
> + continue # Don't use rev3 mini's with this stuff
> + BRANCHES[name]['platforms'][platform][slave_platform]['opt_unittest_suites'] += jittests[:]
> + BRANCHES[name]['platforms'][platform][slave_platform]['debug_unittest_suites'] += jittests[:]
> +
A nit: can you remove the trailing spaces
Attachment #8400152 -
Flags: review?(rail) → review+
| Assignee | ||
Updated•11 years ago
|
Attachment #8400152 -
Flags: checked-in+
Comment 12•11 years ago
|
||
in production.
| Assignee | ||
Comment 13•11 years ago
|
||
verified on tbpl
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
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
•