1339316 - stylo: separate the linux64-stylo talos result from linux64 on perfherder

Status: RESOLVED FIXED

(Testing :: Talos, defect, P3)

Description

[Shing Lyu [:shinglyu]]

If we run talos jobs on `-p linux64-stylo` now, the talos result show up under the linux64 platform instead:

https://treeherder.mozilla.org/#/jobs?repo=try&
revision=6c7d834929a76ff701671a9d0474290d188f1132

(They are actually running a talos build, not a gecko linux64 build because there are stylo specific failures)

This cause the data point on perfherder to be mixed up with other m-c results: 

https://treeherder.mozilla.org/perf.html#/graphs?series=%5Btry,ff2723032e6bee08807c0d0b082c8c6af3dca6f5,1,1%5D&selected=%5Btry,ff2723032e6bee08807c0d0b082c8c6af3dca6f5,169752,76742781%5D

It would be nice if we can move them under the `linux64-stylo` platform instead

Comment 1

[Shing Lyu [:shinglyu]]

Will, do you have any suggestion?

Comment 2

[William Lachance (:wlach)]

(In reply to Shing Lyu [:shinglyu] from comment #1)
> Will, do you have any suggestion?

I would suggesting adding an option to talos called --enable-stylo, similar to what we do already with --disable-e10s.

If set, we would add the extra option "stylo" to the perfherder output:

http://searchfox.org/mozilla-central/source/testing/talos/talos/run_tests.py#187

Eventually we could also use this to enable/disable stylo, once it's behind a preference?

I think it should be pretty straightforward to add this, but let me know if you need any help/pointers.

Comment 3

[Joel Maher ( :jmaher ) (UTC -8)]

I believe this is done