1019792 - [meta] Tracking bug for B2G-testing infastructure buildout

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Infrastructure, defect)

Comment 1

[Stephen Donner [:stephend] Not actively reading bugmail]

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! :)

Comment 2

[raymond [:retornam] (inactive)]

ServiceNow ticket confirms ETA for the 10 Mac Minis to the Mountain View office is Wed, June 18, 2014.

Comment 3

[Malini Das [:mdas] - Away, not checking bugmail]

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

Comment 4

[BMO Automation]

Firefox OS is not being worked on