Closed
Bug 1133871
Opened 10 years ago
Closed 10 years ago
[raptor] Add support for the kk-b2g-emulator to node-mozdevice
Categories
(Firefox OS Graveyard :: Gaia::PerformanceTest, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rwood, Assigned: rwood)
References
Details
Attachments
(8 files)
53 bytes,
text/x-github-pull-request
|
Eli
:
review+
|
Details | Review |
53 bytes,
text/x-github-pull-request
|
Eli
:
review+
|
Details | Review |
46 bytes,
text/x-github-pull-request
|
Eli
:
review+
|
Details | Review |
56 bytes,
text/x-github-pull-request
|
Details | Review | |
57 bytes,
text/x-github-pull-request
|
kgrandon
:
review+
|
Details | Review |
46 bytes,
text/x-github-pull-request
|
Details | Review | |
47 bytes,
text/x-github-pull-request
|
kgrandon
:
review+
|
Details | Review |
46 bytes,
text/x-github-pull-request
|
Details | Review |
The ro.product.model name is different for b2g-emulator-kk vs b2g-emulator; add the b2g-emulator-kk to the node-mozdevice config.json.
Assignee | ||
Comment 1•10 years ago
|
||
We could slip this in the next mozdevice release along with your changes in bug 1129687
Attachment #8566012 -
Flags: review?(eperelman)
Comment 2•10 years ago
|
||
Comment on attachment 8566012 [details] [review]
https://github.com/eliperelman/node-mozdevice/pull/7
Looks good, we will put this in the next release like you said.
Attachment #8566012 -
Flags: review?(eperelman) → review+
Assignee | ||
Comment 3•10 years ago
|
||
Merged:
https://github.com/eliperelman/node-mozdevice/commit/06b44deaf8a8614cb168df77e18e5f910a9b1597
Missed the NPM mozdevice release :( so I need to do another publish and corresponding dependency bump in gaia.
Assignee | ||
Comment 4•10 years ago
|
||
Attachment #8568532 -
Flags: review?(eperelman)
Assignee | ||
Comment 5•10 years ago
|
||
Attachment #8568533 -
Flags: review?(eperelman)
Updated•10 years ago
|
Attachment #8568532 -
Flags: review?(eperelman) → review+
Updated•10 years ago
|
Attachment #8568533 -
Flags: review?(eperelman) → review+
Assignee | ||
Comment 6•10 years ago
|
||
Assignee | ||
Comment 7•10 years ago
|
||
Assignee | ||
Comment 8•10 years ago
|
||
NPM published mozdevice 1.3.1
NPM published gaia-raptor 0.6.1
Comment 9•10 years ago
|
||
Assignee | ||
Comment 10•10 years ago
|
||
Attachment #8568548 -
Flags: review?(kgrandon)
Comment 11•10 years ago
|
||
Comment on attachment 8568548 [details] [review]
https://github.com/mozilla-b2g/gaia-node-modules/pull/96
lgtm!
Attachment #8568548 -
Flags: review?(kgrandon) → review+
Assignee | ||
Comment 12•10 years ago
|
||
Comment 13•10 years ago
|
||
Assignee | ||
Comment 14•10 years ago
|
||
Attachment #8568777 -
Flags: review?(kgrandon)
Comment 15•10 years ago
|
||
Comment on attachment 8568777 [details] [review]
https://github.com/mozilla-b2g/gaia/pull/28427
Lgtm. TBH - I think if you guys are doing reviews on the raptor page, it should be fine for you to self-review simple manifest bumps for gaia-node-modules and gaia. If you want an extra set of eyes, feel free to ping me, but I'm not sure it's necessary every time :)
Attachment #8568777 -
Flags: review?(kgrandon) → review+
Assignee | ||
Comment 16•10 years ago
|
||
Ok sounds good, thanks Kevin!
Assignee | ||
Comment 17•10 years ago
|
||
Sorry to bug you guys, but on the gaia try run, there's a test failure, and I'm not really sure why... any ideas?
17:49:04 INFO - Error: timeout exceeded!
17:49:04 INFO - at Object.Client.waitForSync (/builds/slave/test/gaia/node_modules/marionette-client/lib/marionette/client.js:693:16)
17:49:04 INFO - at Object.Client.waitFor (/builds/slave/test/gaia/node_modules/marionette-client/lib/marionette/client.js:661:60)
17:49:04 INFO - at Object.MarionetteHelper.waitForElement (/builds/slave/test/gaia/node_modules/marionette-helper/index.js:142:12)
17:49:04 INFO - at Object.switchProvidersSelect (/builds/slave/test/gaia/apps/search/test/marionette/lib/search.js:128:31)
17:49:04 INFO - at Context.<anonymous> (/builds/slave/test/gaia/apps/search/test/marionette/change_providers_test.js:59:24)
17:49:04 INFO - at callFn (/builds/slave/test/gaia/node_modules/mocha/lib/runnable.js:223:21)
17:49:04 INFO - at Test.Runnable.run (/builds/slave/test/gaia/node_modules/mocha/lib/runnable.js:216:7)
17:49:04 INFO - at Runner.runTest (/builds/slave/test/gaia/node_modules/mocha/lib/runner.js:373:10)
17:49:04 INFO - at /builds/slave/test/gaia/node_modules/mocha/lib/runner.js:451:12
17:49:04 INFO - at next (/builds/slave/test/gaia/node_modules/mocha/lib/runner.js:298:14)
17:49:04 INFO - at /builds/slave/test/gaia/node_modules/mocha/lib/runner.js:308:7
17:49:04 INFO - at next (/builds/slave/test/gaia/node_modules/mocha/lib/runner.js:246:23)
17:49:04 INFO - at /builds/slave/test/gaia/node_modules/mocha/lib/runner.js:270:7
17:49:04 INFO - at done (/builds/slave/test/gaia/node_modules/mocha/lib/runnable.js:185:5)
17:49:04 INFO - at callFn (/builds/slave/test/gaia/node_modules/mocha/lib/runnable.js:228:7)
17:49:04 INFO - at Hook.Runnable.run (/builds/slave/test/gaia/node_modules/mocha/lib/runnable.js:216:7)
17:49:04 INFO - at next (/builds/slave/test/gaia/node_modules/mocha/lib/runner.js:258:10)
17:49:04 INFO - at /builds/slave/test/gaia/node_modules/mocha/lib/runner.js:270:7
17:49:04 INFO - at done (/builds/slave/test/gaia/node_modules/mocha/lib/runnable.js:185:5)
17:49:04 INFO - at /builds/slave/test/gaia/node_modules/mocha/lib/runnable.js:199:9
17:49:04 INFO - at Object.executeHook (/builds/slave/test/gaia/node_modules/marionette-client/lib/marionette/client.js:371:18)
17:49:04 INFO - at process._tickCallback (node.js:415:13)
Flags: needinfo?(kgrandon)
Flags: needinfo?(eperelman)
Comment 18•10 years ago
|
||
Comment 19•10 years ago
|
||
This may have been due to a previous error on master. I suggest re-basing and trying again over the top. I've gone ahead and submitted a pull request with your commit to see what gaia-try does in case I beat you to it.
Flags: needinfo?(kgrandon)
Flags: needinfo?(eperelman)
Comment 20•10 years ago
|
||
I agree with Kevin. It's VERY unlikely any of the Raptor changes could be affecting any of these tests. More likely is there is some other failure. Either re-trigger the test, or rebase your patch against master and push again so there are new tests run.
Comment 21•10 years ago
|
||
Latest test run looks good. In master: https://github.com/mozilla-b2g/gaia/commit/00272b56366bf2f6c09420efa858b07eac339158
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•