Closed Bug 512321 Opened 15 years ago Closed 15 years ago

hit setupBuild exception at the start of l10nverify in firefox 3.5.3 release

Categories

(Release Engineering :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: bhearsum)

References

Details

Attachments

(2 files)

Probably an import/reload problem tripped by the master splitout.
Here's the exception:
2009/08/24 13:47 PDT [HTTPChannel,260,10.2.72.11] 10.2.72.11 - - [24/Aug/2009:20        --- <exception caught here> ---
          File "/tools/buildbot/lib/python2.5/site-packages/buildbot/process/base.py", line 351, in startBuild
            self.setupBuild(expectations) # create .steps
          File "/tools/buildbot/lib/python2.5/site-packages/buildbot/process/base.py", line 401, in setupBuild
            step = factory(**args)
          File "/tools/buildbotcustom/buildbotcustom/steps/release.py", line 28, in __init__
            TinderboxShellCommand.__init__(self, ignoreCodes=[0,1], **kwargs)
        <type 'exceptions.TypeError'>: unbound method __init__() must be called with TinderboxShellCommand instance as first argument (got L10nVerifyMetaDiff instance instead)
I'm pretty sure this is caused by the double reload of buildbotcustom.steps.misc - one by factory.py, and another in steps/release.py. The former is called first, when misc.py gets imported. The latter is done when release_master.py gets processed.

Let's try removing the second one. steps/release.py's only consumer is factory.py (and ccfactory.py, which is a consumer of factory.py) so we should be able to safely remove it.
Attachment #396290 - Flags: review?(nthomas)
Attachment #396290 - Flags: review?(nthomas) → review+
Comment on attachment 396290 [details] [diff] [review]
removed second reload of buildbotcustom.steps.misc

changeset:   397:9a587b917756
Attachment #396290 - Flags: checked-in+
The first patch didn't work. buildbotcustom.steps.release ended up with the current buildbotcustom.steps.misc, but when buildbotcustom.misc was reloaded in master2.cfg the buildbotcustom.steps.misc address changed. If we reload buildbotcustom.misc before buildbotcustom.steps.release grabs the outdated address we should be fine (no really).
Attachment #396294 - Flags: review?(nthomas)
Attachment #396294 - Flags: review?(nthomas) → review+
Comment on attachment 396294 [details] [diff] [review]
move buildbotcustom.misc import

ichangeset:   1462:5b1820fab855
Attachment #396294 - Flags: checked-in+
The combination of these two patches fixed us up.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
No longer blocks: 511469
Blocks: 511469
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: