1020215 - Set up Flame device in Eideticker CI

Status: RESOLVED FIXED

(Testing Graveyard :: Eideticker, defect, P1)

Description

[Dave Hunt [:davehunt] [he/him] ⌚GMT]

We need to gather results for Flame and push them to our dashboard at http://eideticker.mozilla.org/b2g/

Comment 1

[Dave Hunt [:davehunt] [he/him] ⌚GMT]

We now have a Flame device attached to Eideticker CI but we have not yet had a successful test run. I'll file blocking bugs as I encounter them.

Comment 2

[Dave Hunt [:davehunt] [he/him] ⌚GMT]

Attachment: Add support for Flame device. v1.0

Note there are still a number of blockers, but I don't expect them to affect this patch.

Comment 3

[William Lachance (:wlach)]

Comment on attachment 8441974 [details] [diff] [review]
Add support for Flame device. v1.0

Review of attachment 8441974 [details] [diff] [review]:
-----------------------------------------------------------------

Looks reasonable, though I think the orng/ntpclient pushing is a bit overcomplicated.

::: jenkins-master/buildstep-config-files.xml
@@ +24,2 @@
>  adb shell su -c chmod 700 /data/local/orng
> +adb shell su -c rm $1/orng</content>

I think you could just do adb push orng /data/local/orng and save some steps here.

@@ +210,5 @@
>          <name>Install NTP client</name>
>          <comment>Install NTP client on the device</comment>
>          <content>#!/bin/bash -ex
> +adb push ntpclient $1
> +adb shell su -c dd if=$1/ntpclient of=/data/local/ntpclient

Ditto.

Comment 4

[Dave Hunt [:davehunt] [he/him] ⌚GMT]

Landed with suggested changes:
https://github.com/mozilla/eideticker-ci/commit/1a9603fa327d5610550a174cf050fbc24ad25544

I've also deployed these changes:
http://eideticker-ci1.ateam.phx1.mozilla.com:8080/

Comment 5

[Dave Hunt [:davehunt] [he/him] ⌚GMT]

Results have now started to appear at http://eideticker.mozilla.org/b2g