Closed
Bug 829481
Opened 13 years ago
Closed 13 years ago
SeaMonkey Windows builds fail with "python.exe: Bad file number" error
Categories
(SeaMonkey :: Release Engineering, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mcsmurf, Assigned: mcsmurf)
Details
Attachments
(1 file)
|
714 bytes,
patch
|
ewong
:
review+
|
Details | Diff | Splinter Review |
Starting with this checkin http://hg.mozilla.org/comm-central/rev/bc4fa652cdf7 the SeaMonkey Windows builds fail with this error:
e:/builds/slave/comm-cen-trunk-w32/build/objdir/mozilla/_virtualenv/Scripts/python.exe /e/builds/slave/comm-cen-trunk-w32/build/mozilla/config/nsinstall.py -t "/e/builds/slave/comm-cen-trunk-w32/build/mozilla/content/base/test/test_bug459424.html" [...deleting very long list of files here...] "/e/builds/slave/comm-cen-trunk-w32/build/mozilla/content/base/test/file_bothCSPheaders.html" "/e/builds/slave/comm-cen-trunk-w32/build/mozilla/content/base/test/file_bothCSPheaders.html^headers^" ../../../_tests/testing/mochitest/tests/content/base/test
make[7]: Leaving directory `/e/builds/slave/comm-cen-trunk-w32/build/objdir/mozilla/content/base/test'
make[6]: Leaving directory `/e/builds/slave/comm-cen-trunk-w32/build/objdir/mozilla/content/base'
make[5]: Leaving directory `/e/builds/slave/comm-cen-trunk-w32/build/objdir/mozilla/content'
make[4]: Leaving directory `/e/builds/slave/comm-cen-trunk-w32/build/objdir/mozilla'
make[3]: Leaving directory `/e/builds/slave/comm-cen-trunk-w32/build/objdir/mozilla'
make[2]: Leaving directory `/e/builds/slave/comm-cen-trunk-w32/build/objdir/mozilla'
make[1]: Leaving directory `/e/builds/slave/comm-cen-trunk-w32/build/objdir'
make[2]: Leaving directory `/e/builds/slave/comm-cen-trunk-w32/build/objdir/mozilla'
make[1]: Leaving directory `/e/builds/slave/comm-cen-trunk-w32/build/objdir'
/bin/sh: e:/builds/slave/comm-cen-trunk-w32/build/objdir/mozilla/_virtualenv/Scripts/python.exe: Bad file number
make[7]: *** [libs] Error 126
make[6]: *** [tools] Error 2
make[5]: *** [base_tools] Error 2
make[4]: *** [tools_tier_platform] Error 2
make[3]: *** [tier_platform] Error 2
make[2]: *** [default] Error 2
make[1]: *** [default] Error 2
make: *** [build] Error 2
program finished with exit code 2
This looks a bit like Bug 817576.
| Assignee | ||
Comment 1•13 years ago
|
||
Justin: It looks like we need to push this checkin http://hg.mozilla.org/build/buildbotcustom/rev/1581c6ae51d8 to the seamonkey-production branch. Should I take care of that?
| Assignee | ||
Comment 2•13 years ago
|
||
Actually, now that I look at this again, this checkin would not work for us. I guess we would need to shorten "comm-cen-trunk-w32" somehow.
Comment 3•13 years ago
|
||
I'll look at this ASAP, probably mid-next-week or so (I'll be in TOR the whole week, so no promises), but getting SM on [using] Py2.7 is first priority, fixing this is second.
Assignee: nobody → bugspam.Callek
| Assignee | ||
Comment 4•13 years ago
|
||
I already know how to fix this.
| Assignee | ||
Comment 5•13 years ago
|
||
This should fix it, the patch replaces comm with c and trunk with t in the objdir.
Attachment #700955 -
Flags: review?(bugspam.Callek)
Comment 6•13 years ago
|
||
Comment on attachment 700955 [details] [diff] [review]
Patch
Review of attachment 700955 [details] [diff] [review]:
-----------------------------------------------------------------
This looks good. I just need to coordinate it with the builddir changes in the database before I push this out and reconfig.
Attachment #700955 -
Flags: review?(bugspam.Callek) → review+
Updated•13 years ago
|
Component: Build Config → Release Engineering
| Assignee | ||
Comment 7•13 years ago
|
||
Pushed to seamonkey-production branch: http://hg.mozilla.org/build/buildbotcustom/rev/888749cb9d6a
Comment 8•13 years ago
|
||
Win builds are back to green. Thanks for the patch, mcsmurf!
Closing this bug.
Assignee: bugspam.Callek → bugzilla
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 9•13 years ago
|
||
> Win builds are back to green.
I think you mean orangey sort of green.
You need to log in
before you can comment on or make changes to this bug.
Description
•