59.92% sccache hit rate (linux64-shippable) regression on push d2fc2720837c81d95d97eaa1539c7fe1bcbb2beb (Fri August 30 2019)
Categories
(Developer Infrastructure :: Lint and Formatting, defect)
Tracking
(Not tracked)
People
(Reporter: marauder, Unassigned)
References
(Regression)
Details
(Keywords: regression)
We have detected a build metrics regression from push:
As author of one of the patches included in that push, we need your help to address this regression.
Regressions:
60% sccache hit rate linux64-shippable opt instrumented 0.99 -> 0.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=22905
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
*** Please let us know your plans within 3 business days, or the offending patch(es) will be backed out! ***
Reporter | ||
Updated•5 years ago
|
Comment 1•5 years ago
•
|
||
I'm not really sure how my patch would have affected this. The only thing that I can think of that is even remotely conceivable is that it adds build/pymake
to the list of third party paths in tools/rewriting/ThirdPartyPaths.txt
:
https://hg.mozilla.org/integration/autoland/rev/6c0e88788302e6807ef53e4d5aa7fc9e89b44487#l4.5
Chris, do you think that could somehow affect the sccache hit rate?
If not I would strongly suspect that my change was unrelated and whatever caused the regression was something external to mozilla-central (and my push just happened to be the first unlucky one to display it).
If so, I guess we can remove build/pymake
from ThirdPartyPaths.txt and instead add it to the exclude list in the license linter.
Comment 3•5 years ago
|
||
Judging by the graph:
it's far far more likely that this is caused by:
which is to be expected from a compiler change.
Reporter | ||
Comment 4•5 years ago
|
||
Thanks for the updates!
Updated•2 years ago
|
Updated•2 years ago
|
Description
•