We have detected a build metrics regression from push 6b410448e079878a8414a6718efc6f4c2bfad001. As author of one of the patches included in that push, we need your help to address this regression. Regressions: 2% sccache requests_not_cacheable summary android-4-2-x86 opt taskcluster-c4.2xlarge 39.17 -> 40 You can find links to graphs and comparison views for each of the above tests at: https://treeherder.mozilla.org/perf.html#/alerts?id=6087 On the page above you can see an alert for each affected platform as well as a link to a graph showing the history of scores for this test. There is also a link to a treeherder page showing the jobs in a pushlog format. To learn more about the regressing test(s), please see: https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Automated_Performance_Testing_and_Sheriffing/Build_Metrics

This is not serious enough to worry about. In general, the requests_not_cacheable number is mostly there to check that we didn't completely break our ability to use sccache--if it jumps from 40 to 2000 or something like that, we'd be worried.

(In reply to Ted Mielczarek [:ted.mielczarek] from comment #1) > This is not serious enough to worry about. In general, the > requests_not_cacheable number is mostly there to check that we didn't > completely break our ability to use sccache--if it jumps from 40 to 2000 or > something like that, we'd be worried. So we should be setting the threshold for regressions somewhat higher for this metric?

Yes. I don't know what the right value is, but 2% is clearly too low.

:ted.mielczarek Thanks for making this clear. Will file a bug to update the threshold.

I filed bug 1358098 for this.