Merge lp:~gmb/launchpad/remove-bug-heat-from-garbo-daily-bug-511283 into lp:launchpad/db-devel

[Graham Binns]

BugHeatUpdater is no longer run as part of garbo-daily.

[Graham Binns (gmb)]

Don't run BugHeatUpdater as part of garbo-daily.

[Gavin Panella (allenap)]

review: Approve (code)

[Graham Binns (gmb)]

I've requested a release-critical for this branch since without it there's a good chance that garbo-daily will take well over 30 hours to run after the rollout. That's not so clever an attribute in a daily script.

Note that this would have landed on Friday but for unrelated buildbot failures.

[Graham Binns (gmb)]

Also note that no tests have been changed; due to the nature of the garbo tests that was unnecessary.

[Gary Poster (gary)]

Hi Graham. I'm trying for the guideline of "if it would have been a CP, it can be a release-critical". The problem you say it addresses does sound like it would be a CP candidate under non-release circumstances, but could you verify before I pursue further?

[Gary Poster (gary)]

Graham verified that this is a CP-equivalent, and gave a few more details.

review: Approve (release-critical)

=== modified file 'lib/canonical/launchpad/scripts/garbo.py'
--- lib/canonical/launchpad/scripts/garbo.py	2010-01-12 16:51:27 +0000
+++ lib/canonical/launchpad/scripts/garbo.py	2010-01-22 18:08:15 +0000
@@ -857,7 +857,6 @@
         PersonEmailAddressLinkChecker,
         BugNotificationPruner,
         BranchJobPruner,
-        BugHeatUpdater,
         ]
     experimental_tunable_loops = [
         PersonPruner,