Closed
Bug 1132179
Opened 9 years ago
Closed 9 years ago
[raptor] Allow custom configurations of devices for performance testing
Categories
(Firefox OS Graveyard :: Gaia::PerformanceTest, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ikumar, Assigned: Eli)
References
Details
(Keywords: perf, Whiteboard: [caf priority: p2][CR 795090])
Attachments
(3 files)
There exist devices that are not available to everyone for various reasons - not enough to share, can’t share, don't want to share - so a centralized device repository doesn't work.
Blocks: CAF-v2.2-metabug
Keywords: perf
Updated•9 years ago
|
Assignee: nobody → eperelman
Assignee | ||
Comment 1•9 years ago
|
||
I see the solution to this being either an environment variable flag pointing to a custom configuration file, or Raptor determines a conventional location for a custom configuration file to exist.
Updated•9 years ago
|
Whiteboard: [CR 795090]
Updated•9 years ago
|
Whiteboard: [CR 795090] → [caf priority: p2][CR 795090]
Updated•9 years ago
|
Blocks: PerformanceProgram
Comment 2•9 years ago
|
||
(In reply to :Eli Perelman from comment #1) > I see the solution to this being either an environment variable flag > pointing to a custom configuration file, or Raptor determines a conventional > location for a custom configuration file to exist. Passing in as a flag sounds like the most convenient option. "conventional location" sounds like modification/population of files in the src area which we'd like to continue to avoid.
Comment 3•9 years ago
|
||
Flagging Ravi on this to provide context and blocking rationale that are missing from the original description and nomination.
Flags: needinfo?(rdandu)
Comment 4•9 years ago
|
||
[Blocking Requested - why for this release]: This should not block 2.2. It is not a device side bug, this is on a new tool which tracks performance.
Flags: needinfo?(rdandu)
Comment 5•9 years ago
|
||
Ravi, Per my triage with CAF today, a fix for this issue is still needed for them to use Raptor that implies that this issue needs to be 2.2+ blocking-b2g or feature-b2g. Is there a reason why neither flag was set or 2.2? cleared? Thanks, Mike
Flags: needinfo?(rdandu)
Comment 6•9 years ago
|
||
Clarified with :eli on IRC that Raptor delivery is planned for end of Q1 which aligns with the current 2.2 FC date of April 6th at https://wiki.mozilla.org/B2G/Roadmap This means Raptor is scheduled to be delivered for 2.2 FC and not 2.2 FL.
Flags: needinfo?(rdandu)
Assignee | ||
Comment 7•9 years ago
|
||
Attachment #8571381 -
Flags: review?(rwood)
Comment 8•9 years ago
|
||
Comment on attachment 8571381 [details] [review] Link to Github pull-request: https://github.com/eliperelman/node-mozdevice/pull/9 LGTM and works great. Removed the emulator-kk from the node-mozdevice/config.json, added it to a separate config.json, then provided that second config as MOZDEVICE_CONFIG and the raptor emulator launch test ran fine.
Attachment #8571381 -
Flags: review?(rwood) → review+
Comment 9•9 years ago
|
||
Assignee | ||
Comment 10•9 years ago
|
||
Comment on attachment 8572026 [details] [review] [gaia-node-modules] eliperelman:bug-1132179 > mozilla-b2g:master Carrying over r+.
Attachment #8572026 -
Flags: review+
Comment 11•9 years ago
|
||
Assignee | ||
Comment 12•9 years ago
|
||
Comment on attachment 8572027 [details] [review] [gaia] eliperelman:bug-1132179 > mozilla-b2g:master Carrying over r+.
Attachment #8572027 -
Flags: review+
Assignee | ||
Comment 13•9 years ago
|
||
Try run: https://treeherder.mozilla.org/#/jobs?repo=gaia-try&revision=b54faf8f0144 In master: https://github.com/mozilla-b2g/gaia/commit/66233b9384a7addc2c06fbde7531bb96e68fcdd8
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
blocking-b2g: 2.2? → ---
Blocks: CAF-v3.0-FL-metabug
No longer blocks: CAF-v3.0-FL-metabug
Updated•9 years ago
|
No longer blocks: PerformanceProgram
You need to log in
before you can comment on or make changes to this bug.
Description
•