Mobile/Testing/11 02 16: Difference between revisions
Jump to navigation
Jump to search
(→Autophone: Mw on inbound) |
|||
Line 30: | Line 30: | ||
** too much variability in results. not sure if soak time will help. | ** too much variability in results. not sure if soak time will help. | ||
* Waiting on asset tags before shipping to Mountain View | * Waiting on asset tags before shipping to Mountain View | ||
* [dminor] Is there anything blocking running Mw job on inbound/autoland? | |||
** Cw seems to be doing ok and not running very often... | |||
== Perfherder == | == Perfherder == |
Revision as of 16:55, 2 November 2016
Previous Action Items
Status reports
Dev team
Rel Eng
A Team
- (buildbot) android-4-3-armv7-api15 Total failure rate: [3.09%]
- last week 3.21%
- total failure excluding retries 1.4%
- (taskcluster) android-4-3-armv7-api15 Total failure rate: [1.09%]
- last week 4.71%
- total failure excluding retries 0.65%
Data fetched for: 2016-10-25 00:44 — 2016-10-31 18:56
- [gbrown] gave up on Android 6 x86 emulator on aws -- wouldn't complete boot on aws only
Autophone
- Have a rooting technique for the Pixels from Chairfire.
- Rooted nexus-6-{9..18}
- Fixed nexus-5-{2,3,5} that failed to boot by factory resetting the devices.
- Ran tests on all S1S2 tests for samsung-gs3-3, nexus-5-{2,3,5}, nexus-6-{6,9..18}
- treeherder.allizom.org
- phonedash-dev.allizom.org
- nexus 6p devices appear to fall into two groups: a slow group and a fast group.
- too much variability in results. not sure if soak time will help.
- Waiting on asset tags before shipping to Mountain View
- [dminor] Is there anything blocking running Mw job on inbound/autoland?
- Cw seems to be doing ok and not running very often...