This is indeed weird. Under no circumstance bug 1552176 could have caused these regressions. These regressions are all over the place; **all build_metrics** have now changed their baselines. Kim, please bring this heads up to your team. Anyway, this feels to me like an **infra change** actually. But to prove it, we would need to do retriggers which ATM don't work *(more about that in bug 1595359)*. From the considerable infra changes which occurred during this weekend (Nov 9 and 10), after which the build_metrics baselines changed, I think a pretty likely suspect is bug 1546801. Dustin, I am not familiar with work done in this area, so I need your confirmation or clarification here.
Bug 1595498 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This is indeed weird. Under no circumstance bug 1552176 could have caused these regressions. These regressions are all over the place; **all build_metrics** have now changed their baselines, not just sccache. Kim, please bring this heads up to your team. Anyway, this feels to me like an **infra change** actually. But to prove it, we would need to do retriggers which ATM don't work *(more about that in bug 1595359)*. From the considerable infra changes which occurred during this weekend (Nov 9 and 10), after which the build_metrics baselines changed, I think a pretty likely suspect is bug 1546801. Dustin, I am not familiar with work done in this area, so I need your confirmation or clarification here.
This is indeed weird. Under no circumstance bug 1552176 could have caused these regressions. These regressions are all over the place; **all build_metrics** have now changed their baselines, not just sccache. Kim, please bring this heads up to your team. Anyway, this feels to me like an **infra change** actually. But to prove it, we would need to do retriggers on older jobs, which ATM cannot be done *(more about that in bug 1595359)*. From the considerable infra changes which occurred during this weekend (Nov 9 and 10), after which the build_metrics baselines changed, I think a pretty likely suspect is bug 1546801. Dustin, I am not familiar with work done in this area, so I need your confirmation or clarification here.
This is indeed weird. Under no circumstance bug 1552176 could have caused these regressions. These regressions are all over the place; **all build_metrics** have now changed their baselines & remained that way, not just sccache. Kim, please bring this heads up to your team. Anyway, this feels to me like an **infra change** actually. But to prove it, we would need to do retriggers on older jobs, which ATM cannot be done *(more about that in bug 1595359)*. From the considerable infra changes which occurred during this weekend (Nov 9 and 10), after which the build_metrics baselines changed, I think a pretty likely suspect is bug 1546801. Dustin, I am not familiar with work done in this area, so I need your confirmation or clarification here.
This is indeed weird. Under no circumstance bug 1552176 could have caused these regressions. These regressions are all over the place; **all build_metrics** have now changed their baselines **& remained** that way, not just sccache. Kim, please bring this heads up to your team. Anyway, this feels to me like an **infra change** actually. But to prove it, we would need to do retriggers on older jobs, which ATM cannot be done *(more about that in bug 1595359)*. From the considerable infra changes which occurred during this weekend (Nov 9 and 10), after which the build_metrics baselines changed, I think a pretty likely suspect is bug 1546801. Dustin, I am not familiar with work done in this area, so I need your confirmation or clarification here.
This is indeed weird. Under no circumstance bug 1552176 could have caused these regressions. These regressions are all over the place; **all build_metrics** have now changed their baselines **& remained** that way, not just sccache. Kim, please bring this heads up to your team. Anyway, this feels to me like an **infra change** actually. But to prove it, we would need to do retriggers on older jobs, which ATM cannot be done *(more about that in bug 1595359)*. From the considerable infra changes which occurred during this weekend (Nov 9 and 10), after which all the build_metrics baselines changed, I think a pretty likely suspect is bug 1546801. Dustin, I am not familiar with work done in this area, so I need your confirmation or clarification here.
This is indeed weird. Under no circumstance bug 1552176 could have caused these regressions. These regressions are all over the place; **all build_metrics** have now changed their baselines **& remained** that way, not just sccache. Kim, please bring this heads up to your team. Anyway, this feels to me like an **infra change** actually. But to prove it, we would need to do retriggers on older jobs, which ATM cannot be done (more about that in bug 1595359). From the considerable infra changes which occurred during this weekend (Nov 9 and 10), after which all the build_metrics baselines changed, I think a pretty likely suspect is bug 1546801. Dustin, I am not familiar with work done in this area, so I need your confirmation or clarification here.
This is indeed weird. Under no circumstance bug 1552176 could have caused these regressions. These regressions are all over the place; **all build_metrics** have now changed their baselines **& remained** that way, not just sccache. Kim, please bring this heads up to your team. Anyway, this feels to me like an **infra change** actually. But to prove it, we would need to do retriggers on older jobs, which ATM cannot be done (more about that in bug 1595359). From the considerable infra changes which occurred during this weekend (Nov 9 and 10), after which all the build_metrics baselines changed, I think a pretty likely suspect is bug 1546801. Dustin, I am not familiar with work done in this area, so I need your confirmation or clarification here. Tom, I believe you also have the required knowledge to answer this.