Joel Maher ( :jmaher ) (UTC -8) Reporter
	Description • 9 years ago

I have no idea who is the culprit, this points to a merge from m-i, but fx-team has the regression long before m-i:

http://graphs.mozilla.org/graph.html#tests=[[315,132,35],[315,131,35]]&sel=1427634808598.1064,1427999241210.4192&displayrange=30&datatype=geo

a filtered range on treeherder:
https://treeherder.mozilla.org/#/jobs?repo=fx-team&filter-searchStr=Ubuntu HW 12.04 x64 fx-team talos other&fromchange=ab12986b9468&tochange=2c7c65e46790

when we merge into m-i with this c-set included it shows up as the regression.  maybe the issue is the b2g-inbound or something that landed on m-c proper.

here is the list of changesets:
https://hg.mozilla.org/integration/fx-team/pushloghtml?changeset=52979d819dc2

	Joel Maher ( :jmaher ) (UTC -8) Reporter
	Comment 1 • 9 years ago

this is on linux32 as well (and pgo):
http://graphs.mozilla.org/graph.html#tests=[[315,64,33],[315,132,33],[315,131,33]]&sel=1427602951258.2563,1428088142606.01,590.1639344262295,885.2459016393443&displayrange=30&datatype=geo

	Joel Maher ( :jmaher ) (UTC -8) Reporter
	Comment 2 • 9 years ago

this is uplifting to aurora today- we will see if this looks to be a culprit when we get new alerts in.