On Tuesday, June 6, 2017 at 3:17:20 PM UTC-4, Ben Kelly wrote: > On Tue, Jun 6, 2017 at 3:07 PM, Chris Peterson <cpeter...@mozilla.com> > wrote: > > > On 6/6/17 10:33 AM, Boris Zbarsky wrote: > > > >> On 6/1/17 9:04 PM, Mike Hommey wrote: > >> > >>> Ah, forgot to mention that. No, it doesn't affect *our* shipped builds > >>> (because PGO uses a different set of optimization flags). > >>> > >>> But it does affect downstream builds that don't PGO. > >>> > >> > >> Based on the jump I see on June 2 at https://treeherder.mozilla.org > >> /perf.html#/graphs?timerange=2592000&series=%5Bmozilla- > >> central,80984697abf1f1ff2b058e2d9f0b351fd9d12ad9,1,1%5D& > >> series=%5Bmozilla-central,ae68c64ef8bfa104fded89971f1c2c6c90 > >> 926dca,1,1%5D&series=%5Bmozilla-central,dd55da63ebce86ee3867 > >> aa3b39975c2a90869ce2,1,1%5D it affects some of our talos tests too (the > >> ones running on non-pgo). > >> > > > > We stopped Talos testing of non-e10s builds on May 14, but it looks like > > we also stopped testing Linux PGO builds on May 15. Is that expected? > > > > Why did we stop talos testing non-e10s? Firefox for android is a tier 1 > platform (right?) and uses non-e10s. Do we have separate fennec talos > tests somewhere?
We disabled non-e10s talos as we needed bandwidth on our physical hardware to standup new tests (web extensions, quantum pageload with https/mitmproxy). Android is done on Autophone, that is 100% separate and we log the data to perfherder (2 regressions were triaged today!) As for linux64-pgo not having talos data, that was an accident and I filed: https://bugzilla.mozilla.org/show_bug.cgi?id=1370663. Hopefully we can have that resolved. Our focus has been on Windows, so linux/osx has been neglected when it comes to the fine tooth comb. Thanks for bringing this up. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
