Closed Bug 1019792 Opened 7 years ago Closed 3 years ago

[meta] Tracking bug for B2G-testing infastructure buildout

Categories

(Firefox OS Graveyard :: Infrastructure, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: dwong, Unassigned)

References

Details

No description provided.
I want the scope of this tracking bug to be:

Anything and everything (hardware/software alike) that prevents us from delivering on our original, shared goal of being able to (but not limited to, as new needs might arise): run 30+ Flames, connected to stable, performant Wi-Fi and/or cell-data, where they need to be, in a multiple-phone-per-ADB-host configuration (in this case, Mac Minis), with ammeters + remote power-management/device-reset capabilities for both Gaia UI Tests, as well as the JS + Python-based perf tests.

Phew! :)
Depends on: 1016309
Depends on: 1021246
Depends on: 1021247
Depends on: 1023250
Depends on: 1024162
ServiceNow ticket confirms ETA for the 10 Mac Minis to the Mountain View office is Wed, June 18, 2014.
Depends on: 1027316
Blocks: 1027956
Depends on: 1028749
Depends on: 1031375
For greater detail, see https://wiki.mozilla.org/QA/Execution/Web_Testing/Lab but essentially, the goals are:
* build a small capacity (>=8 Flames) automation system running b2gperf and subset of UI tests per gaia commit, flashing gecko periodically from b2g-inbound
    ETA: July 21st 

*     build a higher-capacity (>30 Firefox OS Flames) pool of phones hooked up to mozpool, fully-capable (SIM cards, Wi-Fi, SD cards, etc.), reporting to treeherder
    ETA: Q3
Component: WebQA → Infrastructure
Product: Testing → Firefox OS
OS: Mac OS X → All
Hardware: x86 → All
Summary: [meta] Tracking bug for Web QA B2G-testing infastructure buildout → [meta] Tracking bug for B2G-testing infastructure buildout
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.