1608421 - Investigate if it's useful to run Bugzilla task on autoland

Status: RESOLVED FIXED

(Developer Infrastructure :: Lint and Formatting, task, P3)

Description

[Calixte Denizet (:calixte)]

This task takes around 12 minutes and maybe we could avoid to run it on autoland.

Comment 1

[Marco Castelluccio [:marco]]

If we can't, we should either:

• run it only on outgoing files;
• run it with multiple threads.

Comment 2

[Joel Maher ( :jmaher ) (UTC -8)]

in the last 6 months we have 353 failures of bugzilla and 26993 passes or 1.3% failure - most of those failures are claim-expired, cancelled, or other reasons, only 4 are actual failures.

there are 2 bugs (which are both intermittent infra, retriggers on the job resulted in green) I found responsible for the failures:
https://bugzilla.mozilla.org/show_bug.cgi?id=1623747
https://bugzilla.mozilla.org/show_bug.cgi?id=1481291

The risk of not running this is bugzilla component <-> source file mapping to be out of sync; I think some small breakage if we discover it a day later and fix it in the next m-c merge is acceptable.

While this isn't a lot of money, it reduces load overall and should be simple. I vote for running this on m-c only.

Comment 3

[Marco Castelluccio [:marco]]

Attachment: Bug 1608421 - Only run the bugzilla-components task on mozilla-central. r=jmaher

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/626c3a6cb46b
Only run the bugzilla-components task on mozilla-central. r=jmaher

Comment 5

[Alexandru Michis [:malexandru]]

https://hg.mozilla.org/mozilla-central/rev/626c3a6cb46b

Comment 6

[Sylvestre Ledru [:Sylvestre]]

Comment on attachment 9146614 [details]
Bug 1608421 - Only run the bugzilla-components task on mozilla-central. r=jmaher

Beta/Release Uplift Approval Request

• User impact if declined: None
• Is this code covered by automated tests?: Yes
• Has the fix been verified in Nightly?: Yes
• Needs manual test from QE?: No
• If yes, steps to reproduce:
• List of other uplifts needed: None
• Risk to taking this patch: Low
• Why is the change risky/not risky? (and alternatives if risky): The goal is to disable a job executed for every patch landing in beta or esr.
  We are burning $$$ for no good reason with this job. The job as no action for beta or esr
• String changes made/needed:

ESR Uplift Approval Request

• If this is not a sec:{high,crit} bug, please state case for ESR consideration: Same as for beta
• User impact if declined:
• Fix Landed on Version:
• Risk to taking this patch: Low
• Why is the change risky/not risky? (and alternatives if risky):
• String or UUID changes made by this patch:

Comment 7

[Pascal Chevrel:pascalc]

Comment on attachment 9146614 [details]
Bug 1608421 - Only run the bugzilla-components task on mozilla-central. r=jmaher

Uplift approved for beta and esr, thanks.

Comment 8

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

https://hg.mozilla.org/releases/mozilla-beta/rev/f0784c235ac1

Comment 9

[Julien Cristau [:jcristau]]

https://hg.mozilla.org/releases/mozilla-esr68/rev/2490d49ecf35