1531846 - Include browser/app version in Perfherder data submitted by Raptor

Status: RESOLVED DUPLICATE of bug 1593942

(Testing :: Raptor, enhancement, P2)

Description

[Robert Wood [:rwood]]

Currently the browser version is sent to the control server by the Raptor extension and is included in the final results that are sent, i.e.:

17:40:50 INFO - raptor-control-server received webext_results: {u'subtest_unit': u'ms', u'name': u'raptor-tp6-amazon-firefox', u'type': u'pageload', u'measurements': {u'fcp': [1243, ..., 2389]}, u'subtest_lower_is_better': True, u'browser': u'Firefox 67.0a1 20190301164352', u'lower_is_better': True, u'page': u'https://www.amazon.com/s/url=search-alias%3Daps&field-keywords=laptop', u'unit': u'ms', u'alert_threshold': 2}

It would be good to pass on the browser (or app) version into perfherder via the PERFHERDER_DATA about so it in turn could be picked up by the android health dashboards etc. Also then this is available when it is possible to annotate regressions due to browser version updates.

The PERFHERDER_DATA for Raptor is built here [0] and then dumped out [1]. Perhaps the browser version could be added in the perfherder 'extraOptions' field, I believe that is what we used previously to differentiate when we had e10s vs non-e10s.

[0] https://searchfox.org/mozilla-central/rev/00f3836a87b844b5e4bc82f698c559b9966e4be2/testing/raptor/raptor/output.py#35

[1] https://searchfox.org/mozilla-central/rev/00f3836a87b844b5e4bc82f698c559b9966e4be2/testing/raptor/raptor/output.py#648

Comment 1

[Greg Mierzwinski [:sparky]]

This was finished in bug 1593942. The browser/app name (and version if it's available) are in the 'application' field of the perfherder data.