Bug 1554964 Comment 3 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
(In reply to Ionuț Goldan [:igoldan], Performance Sheriffing from comment #2)
> I know we disabled metrics like these in the past. Should we consider disabling **fcp** also on Windows & re enable Chromium?

I say Windows only, because I noticed the Chromium for OSX restabilized. I made a [try push](https://treeherder.mozilla.org/#/jobs?repo=try&revision=077fb308b07bbb5d9c7a56c234cff75e8a091da6) in which I removed the pinned versions.
Revision 1 by
on 
(In reply to Ionuț Goldan [:igoldan], Performance Sheriffing from comment #2)
> I know we disabled metrics like these in the past. Should we consider disabling **fcp** also on Windows & removed the pinned Chromium versions?

I say Windows only, because I noticed the Chromium for OSX restabilized. I made a [try push](https://treeherder.mozilla.org/#/jobs?repo=try&revision=077fb308b07bbb5d9c7a56c234cff75e8a091da6) in which I removed the pinned versions.
Revision 2 by
on 
(In reply to Ionuț Goldan [:igoldan], Performance Sheriffing from comment #2)
> I know we disabled metrics like these in the past. Should we consider disabling **fcp** also on Windows & removed the pinned Chromium versions?

I say Windows only, because I noticed that Chromium for OSX restabilized. I made a [try push](https://treeherder.mozilla.org/#/jobs?repo=try&revision=077fb308b07bbb5d9c7a56c234cff75e8a091da6) in which I removed the pinned versions.

Back to Bug 1554964 Comment 3