Closed Bug 689669 Opened 14 years ago Closed 14 years ago

Investigate why repackage_jetpack is/isn't being called

Categories

(addons.mozilla.org Graveyard :: Admin/Editor Tools, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: clouserw, Assigned: jbalogh)

Details

We've had a lot of successful repacks of jetpacks show up on AMO, which leads me to believe that this function is working. However, the log()'d statements in the function aren't showing up in our logs anywhere (look at 2011-09-26 and -27).
[jbalogh@syslog1.webapp.phx1 ~]$ bzgrep -c z.jp.repack /var/log/clusterlogs/http_app_addons/2011/09/2011-09-27.bz2 301 [jbalogh@syslog1.webapp.phx1 ~]$ ^27^26^bzgrep -c z.jp.repack /var/log/clusterlogs/http_app_addons/2011/09/2011-09-26.bz2 2465 [jbalogh@syslog1.webapp.phx1 ~]$ bzgrep -c 'z.jp.repack:INFO Repacked <Version: ' /var/log/clusterlogs/http_app_addons/2011/09/2011-09-26.bz2 327 [jbalogh@syslog1.webapp.phx1 ~]$ ^26^27bzgrep -c 'z.jp.repack:INFO Repacked <Version: ' /var/log/clusterlogs/http_app_addons/2011/09/2011-09-27.bz2 25 An example: Sep 27 12:39:08 web3.addons.phx1.mozilla.com: [][] z.jp.repack:INFO Repacked <Version: 1.1.rev3.sdk.1.1> from <Version: 1.1.rev3.sdk.1.0> for <Addon: 331629: Guerapa Desprotetor>
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.