1388636 - 5.06 - 5.08% build times (linux64, windows2012-32) regression on push 32452cb511f50efb743f80d4f9af6f03570b00be (Tue Aug 8 2017)

Status: RESOLVED WONTFIX

(Firefox :: Untriaged, defect)

Description

[Ionuț Goldan [:igoldan]]

We have detected a build metrics regression from push:

https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?changeset=32452cb511f50efb743f80d4f9af6f03570b00be

As author of one of the patches included in that push, we need your help to address this regression.

Regressions:

  5%  build times summary linux64 debug static-analysis taskcluster-c4.4xlarge     1,180.92 -> 1,240.91
  5%  build times summary windows2012-32 debug static-analysis taskcluster-c4.4xlarge1,594.03 -> 1,674.66


You can find links to graphs and comparison views for each of the above tests at: https://treeherder.mozilla.org/perf.html#/alerts?id=8635

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

Comment 1

[Ionuț Goldan [:igoldan]]

Tristan, I see you are the owner of bug 1374024. Is this build time regression something we can improve or accept, due to static analysis benefits, or should we consider a backout? As the owned bug is classified, please add to CC the reviewers also.

Comment 2

[Tristan Bourvon]

This regression is entirely normal, as we just added a new static-analysis checker. We should accept it as it is, knowing that the checker is already fairly optimal in terms of performances.

Comment 3

[Andi [:andi]]

I can confirm what Tristan is saying, this should not be considered as a problem jut a normal fact that occurred adding a new checker that is very valuable. On the other hand the performance penalty for the build time is insignificant.