Closed Bug 603133 Opened 15 years ago Closed 15 years ago

All 1.9.1 tests broken unpacking tests

Categories

(Release Engineering :: General, defect)

defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: philor, Assigned: salbiz)

References

Details

Attachments

(1 file)

See, for example, http://tinderbox.mozilla.org/showlog.cgi?log=Firefox3.5/1286673046.1286673071.15808.gz unpack mochitest tests exception === Output === (crapload of CSS and HTML) <type 'exceptions.ValueError'>: Don't know how to handle firefox-3.5.15pre.en-US.linux-i686.tests.tar.bz2 Traceback (most recent call last): File "/builds/buildbot/build_master4/lib/python2.6/site-packages/buildbot-0.8.1-py2.6.egg/buildbot/process/buildstep.py", line 720, in startStep d.addCallback(self._startStep_2) File "/builds/buildbot/build_master4/lib/python2.6/site-packages/twisted/internet/defer.py", line 224, in addCallback callbackKeywords=kw) File "/builds/buildbot/build_master4/lib/python2.6/site-packages/twisted/internet/defer.py", line 213, in addCallbacks self._runCallbacks() File "/builds/buildbot/build_master4/lib/python2.6/site-packages/twisted/internet/defer.py", line 371, in _runCallbacks self.result = callback(self.result, *args, **kw) --- <exception caught here> --- File "/builds/buildbot/build_master4/lib/python2.6/site-packages/buildbot-0.8.1-py2.6.egg/buildbot/process/buildstep.py", line 755, in _startStep_2 skip = self.start() File "/builds/buildbot/build_master4/lib/python2.6/site-packages/buildbotcustom/steps/misc.py", line 437, in start raise ValueError("Don't know how to handle %s" % filename) exceptions.ValueError: Don't know how to handle firefox-3.5.15pre.en-US.linux-i686.tests.tar.bz2 === Output ended === I take it nobody actually looked at Firefox3.5 (before or) after the "only unpack the tests we need for a suite" patch landed?
I closed the 1.9.1 tree.
Syed, could you please look at this ? The basic problem is that 1.9.1 still uses bz2 compression for test archives, and everything else moved to zip files.
Assignee: nobody → salbiz
Blocks: 594018
I didn't realize we were using tarballs for any of the tests and neglected to account for that in my patch. This patch simply falls back to the previous behaviour and unpacks the whole thing if it comes across a tarball during unpackTest. Alternatively, I could also re-factor the logic to selectively unpack tests for both tarballs and zips, but that will require a bit more testing to make sure everything works properly.
Attachment #482546 - Flags: feedback?(catlee)
Attachment #482546 - Flags: feedback?(catlee) → feedback+
Comment on attachment 482546 [details] [diff] [review] fall back to default unpackFile behaviour for tarballs [Tested] Did a quick staging run to make sure it works.
Attachment #482546 - Attachment description: fall back to default unpackFile behaviour for tarballs → fall back to default unpackFile behaviour for tarballs [Tested]
Attachment #482546 - Flags: review?(catlee)
Attachment #482546 - Flags: checked-in?
Attachment #482546 - Flags: review?(catlee) → review+
Flags: needs-reconfig?
Comment on attachment 482546 [details] [diff] [review] fall back to default unpackFile behaviour for tarballs [Tested] http://hg.mozilla.org/build/buildbotcustom/rev/a6ac1ffd5e79
Attachment #482546 - Flags: checked-in? → checked-in+
Flags: needs-reconfig? → needs-reconfig+
Lots of green tests on Firefox3.5 now.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Reopened 3.5 tree too.
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: