Closed
Bug 629503
Opened 14 years ago
Closed 14 years ago
copy tp4.manifest to mobile_tp4.manifest, cut pages from mobile_tp4.manifest until n900s go green, then put live
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mozilla, Assigned: mozilla)
References
Details
Attachments
(3 files, 7 obsolete files)
1.10 KB,
text/plain
|
Details | |
10.76 KB,
patch
|
jhford
:
review+
mozilla
:
checked-in+
|
Details | Diff | Splinter Review |
13.33 KB,
patch
|
mozilla
:
review+
|
Details | Diff | Splinter Review |
Per DougT.
Higher priority than release work per Stuart.
Comment 1•14 years ago
|
||
This manifest is a cut down version of the full tp4 manifest. It has 25 sites, instead of the 100 sites in the full manifest. The 25 sites are a mix of languages, I didn't try to focus on English only.
How I choose the sites is arbitrary, but we don't have a real mobile-specific pageset yet.
Assignee | ||
Comment 2•14 years ago
|
||
Also update mobile.config to point to it.
N900 talos jobs download talos from a tarball.
I'll update the staging tarball with this patch and let it run tp4 for a while.
It should report to the MobileTest tinderbox tree:
http://tinderbox.mozilla.org/showbuilds.cgi?tree=MobileTest
Assignee | ||
Comment 3•14 years ago
|
||
Running in staging. MobileTest may be behind since tinderbox.m.o was having issues earlier, or I may have something to fix.
I'll keep these running and report on status; hopefully they'll show up on tinderbox soon.
Assignee | ||
Comment 4•14 years ago
|
||
Assignee | ||
Comment 5•14 years ago
|
||
The chrome-enabled tp4 runs don't even list the pages they're loading.
Assignee | ||
Comment 6•14 years ago
|
||
Same with the qt non-nochrome (chrome) run -- no pages listed.
I'm going to guess this is a side effect of pageloader in e10s?
Assignee | ||
Comment 7•14 years ago
|
||
this looks similar to the n900-qt tp4 nochrome run.
Assignee | ||
Comment 8•14 years ago
|
||
We're orange across the board with the smaller pageset. We're not finishing cycle 1, let alone 3 cycles of 25 pages.
Assignee | ||
Comment 9•14 years ago
|
||
Ok, these are starting to show up on MobileTest so I'll stop pasting logs. (Ignore the reds; these are orange).
8/8 runs are orange so far.
Comment 10•14 years ago
|
||
Something is busted trying to start the test. We don't even make it to the real test. Looks like a e10s issue, but it should work since we use the pageloader for other tests.
I can try this on my N900
Comment 11•14 years ago
|
||
This smaller manifest removes a few pages that were crashing Fennec running Tp with chrome (e10s mode). I can successfully run Tp4 with this manifest on my N900.
I have a patch to pageloader to allow it to run using chrome (e10s mode). The nochrome mode should work OK with this smaller manifest too.
Comment 12•14 years ago
|
||
Needs patched pageloader (bug 629691) and a "-tpdelay 1000" in the config. I can pass 3 cycles on my N900
Depends on: 629691
Assignee | ||
Updated•14 years ago
|
Attachment #507865 -
Attachment mime type: text/cache-manifest → text/plain
Assignee | ||
Comment 13•14 years ago
|
||
With this patch, and the pageloader patch from bug 629691, the staging n900s running m-c tp4 (gtk, gtk nochrome, qt, qt nochrome) all went green.
Attachment #507730 -
Attachment is obsolete: true
Attachment #507734 -
Attachment is obsolete: true
Attachment #507749 -
Attachment is obsolete: true
Attachment #507756 -
Attachment is obsolete: true
Attachment #507757 -
Attachment is obsolete: true
Attachment #507758 -
Attachment is obsolete: true
Attachment #508076 -
Flags: review?(jmaher)
Assignee | ||
Comment 14•14 years ago
|
||
Also remove the obsolete non-n900 configs.
Attachment #508077 -
Flags: review?(jhford)
Comment 15•14 years ago
|
||
Great stuff! After watching MobileTest for a bit, I see some orange, but I'm not sure how much is OOM and how much is crashes in X. In any case, we are doing much better now.
Comment 16•14 years ago
|
||
Comment on attachment 508076 [details] [diff] [review]
talos patch with mfinkle's changes
we should make the same change to remote.config as well. Also we will be testing a much smaller set of web pages on each build, so our 'coverage' is reduced. We should consider running a full cycle for functionality testing instead of performance testing. All of this feedback belongs in other bugs.
Attachment #508076 -
Flags: review?(jmaher) → review+
Comment 17•14 years ago
|
||
one question I had about this is I don't see -tpdelay on the tdhtml, tsspider, tgfx, and tsvg tests? I think we should be consistent and have all TP style tests act the same.
Comment 18•14 years ago
|
||
this patch supercedes the 'talos patch with mfinkle's changes' such that it adds the -tpdelay to all TP style tests and replicates all these changes from mobile.config into remote.config as well.
Attachment #508427 -
Flags: review?(aki)
Updated•14 years ago
|
Attachment #508077 -
Flags: review?(jhford) → review+
Assignee | ||
Comment 19•14 years ago
|
||
Comment on attachment 508427 [details] [diff] [review]
update all tp tests and remote.config with tpdelay changes (1.0)
I've got this running on n900s in staging.
Assignee | ||
Comment 20•14 years ago
|
||
Comment on attachment 508427 [details] [diff] [review]
update all tp tests and remote.config with tpdelay changes (1.0)
I'm ok with this, as long as the mobile team knows that their numbers may shift when this lands.
Attachment #508427 -
Flags: review?(aki) → review+
Assignee | ||
Updated•14 years ago
|
Attachment #508076 -
Attachment is obsolete: true
Comment 21•14 years ago
|
||
Assignee | ||
Comment 22•14 years ago
|
||
Comment on attachment 508077 [details] [diff] [review]
enable running tp4 in production on n900s
http://hg.mozilla.org/build/buildbot-configs/rev/87d7d09620cd
Attachment #508077 -
Flags: checked-in+
Assignee | ||
Comment 23•14 years ago
|
||
production-mobile-master reconfiged. I think we're done here.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•