Closed Bug 1118270 Opened 8 years ago Closed 8 years ago

[raptor] Add emulator option and set timeout accordingly

Categories

(Firefox OS Graveyard :: Gaia::PerformanceTest, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rwood, Assigned: rwood)

References

Details

Attachments

(3 files)

To support running raptor tests on the b2g-emulator, add an emulator command line / env var option. If RAPTOR_EMULATOR=1, the raptor timeout value will be set accordingly for the emulator (as the emulator is much slower than device).

Need to add an option instead of just grabbing the device model, because b2g is restarted before the orng instance is created; and we need to have the timeout set before the intial b2g restart. Also I imagine there will be other places the options.emulator flag will be used as raptor on b2g-emulator support is further developed anyway.
Attachment #8544614 - Flags: review?(eperelman)
Attachment #8544614 - Flags: review?(eperelman) → review+
Updated PR to bump raptor package version to 0.2.0, and orng dependency to 0.3.0, and merged:
https://github.com/mozilla-b2g/raptor/commit/dfbec31084752e851de670c4d84f88e64c94968e
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Comment on attachment 8545287 [details] [review]
Link to Github pull-request: https://github.com/mozilla-b2g/gaia-node-modules/pull/85

lgtm.
Attachment #8545287 - Flags: review?(kgrandon) → review+
And there's the PR to update the package.json in gaia to the latest. Seems like we also have a new marionette-js-runner package, so let's wait for gaia-try before landing.
Ran into some problems with the latest marionette-js-runner changes, so I've backed those out from gaia-node-modules, and am re-testing with the latest SHA from that repo.
You need to log in before you can comment on or make changes to this bug.