953128 - Autolog - add Nexus 4 and Nexus 7 jdq39 builds

Status: RESOLVED FIXED

(Testing Graveyard :: Autolog, enhancement)

Description

[Bob Clary [:bc] (inactive)]

Attachment: nexus-jdq39.patch

My nexus 4 and nexus 7 devices are up and running android userdebug builds for s1s2 and mochitest-canvas under Autophone. I need to add their device names to Config.js's OSNames so they will display.

I have chosen nexus-4-jdq39 and nexus-7-jdq39 to include the android build which will allow us to distinguish the newer 2013 nexus 7 when they come online from the older version I currently have. This will also serve to show the relationship between different devices with the same android build. Going forward I believe the use of the android build as part of the device name/description will help distinguish different versions of android.

You can load brasstacks and hack Config.js on brasstacks via a js debugger and add theses devices to Config.js. As more builds are tested, the devices will display the new results so you can see what they look like.

Comment 1

[Bob Clary [:bc] (inactive)]

On second thought, perhaps we should also include the product name and the build name for the Nexus devices at least:

For example, my nexus 7 https://developers.google.com/android/nexus/images#nakasijdq39 would be

nexus-7-nakasi-jdq39 

The new nexus 7 from 2013 https://developers.google.com/android/nexus/images#razorjss15q would be

nexus-7-razor-jss15q

Is that too much?

Comment 2

[Mark Côté [:mcote]]

Comment on attachment 8351458 [details] [diff] [review]
nexus-jdq39.patch

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

If the string is readable and fits fine into autolog and s1s2, I think the more info in there the better. :)

Comment 3

[Jonathan Griffin (:jgriffin)]

Comment on attachment 8351458 [details] [diff] [review]
nexus-jdq39.patch

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

I'm fine with the more detailed names too.

Comment 4

[Bob Clary [:bc] (inactive)]

I went with the original patch at least for now for two reasons:

* I have a couple of weeks of data submitted with this value.
* Autolog does have a problem cutting off long device descriptions/names.

If we wish to revisit this later we can take our time and also fix Autolog's display and update the database at the same time.

http://hg.mozilla.org/automation/autolog/rev/3e96e2f9758d

jgriffin: could you deploy this please?

Comment 5

[Jonathan Griffin (:jgriffin)]

deployed

Comment 6

[Bob Clary [:bc] (inactive)]

jgriffin: I'm getting a Loading failed: error on http://brasstacks.mozilla.com/autolog/?tree=mozilla-central&source=autolog now.

Comment 7

[Bob Clary [:bc] (inactive)]

jgriffin found the issue to be a gs2 failing to include a testgroup_id.
    {
        u'total_test_failures': 4,
        u'testsuite_count': 1,
        u'harness': u'Mochitest-Canvas',
        u'machine': u'98_0c_82_33_ec_8d_samsung-gs2',
        u'platform': u'samsung-gs2',
        u'version': None,
        u'branch': None,
        u'frameworkfailures': None,
        u'total_perf_records': 0,
        u'pending': False,
        u'revision': u'302362be5075',
        u'buildtype': u'opt',
        u'buildid': u'20140106170328',
        u'date': u'2014-01-07',
        u'testrun': u'302362be5075.5',
        u'logurl': None,
        u'testgroup': u'Mochitest-Canvas',
        u'builder': None,
        u'tree': u'mozilla-central',
        u'productname': None,
        u'buildurl': None,
        u'starttime': 1389072711,
        u'os': u'android'
    }

He applied a fix to brasstacks that ignores these malformed results. Not sure what the specific bug in the unittest runner is though.