Closed
Bug 814967
Opened 12 years ago
Closed 11 years ago
Fix includes in mailnews/ .idl files so that builds no longer fail randomly with "error: name 'nsMsgSocketType' specified twice"
Categories
(MailNews Core :: Build Config, defect)
Tracking
(thunderbird19 fixed, seamonkey2.16 fixed)
RESOLVED
FIXED
Thunderbird 20.0
People
(Reporter: mcsmurf, Assigned: mcsmurf)
Details
Attachments
(2 files, 2 obsolete files)
8.46 KB,
patch
|
standard8
:
review+
standard8
:
approval-comm-beta+
|
Details | Diff | Splinter Review |
3.45 KB,
patch
|
standard8
:
review+
standard8
:
approval-comm-beta+
|
Details | Diff | Splinter Review |
SeaMonkey Linux trunk sometimes(?) fails to compile, log from today's nightly build: Traceback (most recent call last): File "/builds/slave/comm-cen-trunk-lnx-ntly/build/mozilla/config/pythonpath.py", line 56, in <module> main(sys.argv[1:]) File "/builds/slave/comm-cen-trunk-lnx-ntly/build/mozilla/config/pythonpath.py", line 48, in main execfile(script, frozenglobals) File "/builds/slave/comm-cen-trunk-lnx-ntly/build/objdir/mozilla/dist/sdk/bin/header.py", line 524, in <module> idl.resolve(options.incdirs, p) File "/builds/slave/comm-cen-trunk-lnx-ntly/build/objdir/mozilla/dist/sdk/bin/xpidl.py", line 287, in resolve p.resolve(self) File "/builds/slave/comm-cen-trunk-lnx-ntly/build/objdir/mozilla/dist/sdk/bin/xpidl.py", line 253, in resolve parent.setName(type) File "/builds/slave/comm-cen-trunk-lnx-ntly/build/objdir/mozilla/dist/sdk/bin/xpidl.py", line 265, in setName self.namemap.set(object) File "/builds/slave/comm-cen-trunk-lnx-ntly/build/objdir/mozilla/dist/sdk/bin/xpidl.py", line 211, in set raise IDLError("name '%s' specified twice. Previous location: %s" % (object.name, self._d[object.name].location), object.location) xpidl.IDLError: error: name 'nsMsgSocketType' specified twice. Previous location: /builds/slave/comm-cen-trunk-lnx-ntly/build/mailnews/base/public/MailNewsTypes2.idl line 38:0 interface nsMsgSocketType { ^, ../../../../mozilla/dist/idl/MailNewsTypes2.idl line 38:0 interface nsMsgSocketType { ^ NEXT ERROR make[7]: *** [_xpidlgen/nsIMsgDatabase.h] Error 1 make[7]: *** Deleting file `_xpidlgen/nsIMsgDatabase.h' make[7]: Leaving directory `/builds/slave/comm-cen-trunk-lnx-ntly/build/objdir/mailnews/db/msgdb/public' make[6]: Leaving directory `/builds/slave/comm-cen-trunk-lnx-ntly/build/objdir/mailnews/db/msgdb' NEXT ERROR make[6]: *** [public_export] Error 2 make[5]: *** [db/msgdb_export] Error 2 make[5]: *** Waiting for unfinished jobs.... http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1353832204.1353832899.27156.gz&fulltext=1#err0
Comment 1•12 years ago
|
||
I'd guess this is fallout from bug 465339. I also see it quite frequently locally (Win7 x64, pymake with -j8).
Assignee | ||
Comment 2•12 years ago
|
||
Here's another build failure, I think it's related so maybe we can fix it here, too: From the Linux 64-bit SeaMonkey tinderbox, build failure in nsIMsgFilter.idl: Traceback (most recent call last): File "/builds/slave/comm-cen-trunk-lnx64-ntly/build/mozilla/config/pythonpath.py", line 56, in <module> main(sys.argv[1:]) File "/builds/slave/comm-cen-trunk-lnx64-ntly/build/mozilla/config/pythonpath.py", line 48, in main execfile(script, frozenglobals) File "/builds/slave/comm-cen-trunk-lnx64-ntly/build/objdir/mozilla/dist/sdk/bin/header.py", line 524, in <module> idl.resolve(options.incdirs, p) File "/builds/slave/comm-cen-trunk-lnx64-ntly/build/objdir/mozilla/dist/sdk/bin/xpidl.py", line 287, in resolve p.resolve(self) File "/builds/slave/comm-cen-trunk-lnx64-ntly/build/objdir/mozilla/dist/sdk/bin/xpidl.py", line 253, in resolve parent.setName(type) File "/builds/slave/comm-cen-trunk-lnx64-ntly/build/objdir/mozilla/dist/sdk/bin/xpidl.py", line 265, in setName self.namemap.set(object) File "/builds/slave/comm-cen-trunk-lnx64-ntly/build/objdir/mozilla/dist/sdk/bin/xpidl.py", line 211, in set raise IDLError("name '%s' specified twice. Previous location: %s" % (object.name, self._d[object.name].location), object.location) xpidl.IDLError: error: name 'nsMsgSocketType' specified twice. Previous location: /builds/slave/comm-cen-trunk-lnx64-ntly/build/mailnews/base/public/MailNewsTypes2.idl line 38:0 interface nsMsgSocketType { ^, ../../../../mozilla/dist/idl/MailNewsTypes2.idl line 38:0 interface nsMsgSocketType { ^ NEXT ERROR make[7]: *** [_xpidlgen/nsIMsgFilter.h] Error 1
Comment 3•12 years ago
|
||
Yes, most likely a result of the same bug. The main thing to do here is to look at the includes in nsIMsgDatabase.idl and see if a) you can replace the include by an "interface" definition, b) reduce where MailNewsTypes2.idl is included in the include tree. Once you've done those, build & compile and add any missing includes as necessary. Same with nsIMsgFilter.idl.
Assignee | ||
Comment 4•12 years ago
|
||
I'm not sure if this is how it should be done, but it works at least. nsIMsgSearchTerm.idl and nsIMsgSearchValue.idl both include nsMsgSearchCore.idl which includes MailNewsTypes2.idl (would it have worked, too if I only had removed one of those two includes?). In nsIMsgDatabase.idl I removed nsIMsgDBView.idl from the include list, it includes MailNewsTypes2.idl. I also removed MailNewsTypes2.idl itself from the include list as it gets included via nsIDBChangeAnnouncer.idl.
Attachment #686506 -
Flags: review?(mbanner)
Assignee | ||
Comment 5•12 years ago
|
||
Forgot to add a change, see Comment 4 for what this patch does.
Attachment #686506 -
Attachment is obsolete: true
Attachment #686506 -
Flags: review?(mbanner)
Attachment #686507 -
Flags: review?(mbanner)
Assignee | ||
Comment 6•12 years ago
|
||
Actually the nsIMsgSearchScopeTerm.idl include (in nsIMsgFilter.idl) includes nsIMsgSearchSession.idl which includes nsIMsgSearchValue.idl which includes nsMsgSearchCore.idl which includes MailNewsTypes2.idl again :)
Assignee | ||
Comment 7•12 years ago
|
||
Need to remove nsIMsgSearchScopeTerm.idl, too as it also includes MailNewsTypes2.idl via the nsIMsgSearchSession.idl include path. Now only nsMsgFilterCore.idl in nsIMsgFilter.idl should include MailNewsTypes2.idl.
Attachment #686511 -
Flags: review?(mbanner)
Assignee | ||
Updated•12 years ago
|
Attachment #686507 -
Attachment is obsolete: true
Attachment #686507 -
Flags: review?(mbanner)
Comment 8•12 years ago
|
||
Try run for c42a35f5a00b is complete. Detailed breakdown of the results available here: https://tbpl.mozilla.org/?tree=Try&rev=c42a35f5a00b Results (out of 11 total builds): success: 9 failure: 2 Builds (or logs if builds failed) available at: http://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/mcsmurf@mcsmurf.de-c42a35f5a00b
Comment 9•12 years ago
|
||
Comment on attachment 686511 [details] [diff] [review] Like this? Review of attachment 686511 [details] [diff] [review]: ----------------------------------------------------------------- Yep, looks good. Thanks.
Attachment #686511 -
Flags: review?(mbanner) → review+
Assignee | ||
Comment 10•12 years ago
|
||
Pushed: https://hg.mozilla.org/comm-central/rev/14a8939f9f47
Assignee: nobody → bugzilla
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 20.0
Assignee | ||
Comment 11•12 years ago
|
||
Appending to this bug here as it's the same issue. A Linux SeaMonkey build failed with the same error message as in Comment 0. The cause is that nsIMsgNewsFolder.idl includes both nsIMsgThread.idl and nsIMsgIncomingServer.idl. Both files include MailNewsTypes2.idl.
Assignee | ||
Comment 12•12 years ago
|
||
reopening because of new patch, pushed patch to try.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 13•12 years ago
|
||
Comment on attachment 696649 [details] [diff] [review] Another patch Compiling this patch worked fine locally (test with -j4 and -j6), it also worked fine on Try: https://tbpl.mozilla.org/?tree=Thunderbird-Try&rev=34cace5c617b. See Comment 11 why this patch is needed.
Attachment #696649 -
Flags: review?(mbanner)
Updated•12 years ago
|
Attachment #696649 -
Flags: review?(mbanner) → review+
Assignee | ||
Comment 14•12 years ago
|
||
Pushed Attachment 696649 [details] [diff]: https://hg.mozilla.org/comm-central/rev/2862496cc60c
Summary: SeaMonkey trunk build failure (nsIMsgDatabase.idl) → Fix includes in mailnews/ .idl files so that builds no longer fail randomly with "error: name 'nsMsgSocketType' specified twice"
Assignee | ||
Comment 15•11 years ago
|
||
Resolving for now, I think I saw another occurrence of this bug a few weeks ago. But I'll file a new bug then if I see this happen again.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 11 years ago
Resolution: --- → FIXED
Comment 16•11 years ago
|
||
Comment on attachment 686511 [details] [diff] [review] Like this? I'm seeing this on today's SeaMonkey beta build, assuming the patch applies, Mark can I get you're approval to land [I think these are safe to land]
Attachment #686511 -
Flags: approval-comm-beta?
Comment 17•11 years ago
|
||
Comment on attachment 696649 [details] [diff] [review] Another patch Review of attachment 696649 [details] [diff] [review]: ----------------------------------------------------------------- I'm seeing this on today's SeaMonkey beta build, assuming the patch applies, Mark can I get you're approval to land [I think these are safe to land]
Attachment #696649 -
Flags: approval-comm-beta?
Comment 18•11 years ago
|
||
I'll note these two patches are already on aurora. And that SeaMonkey Council has not been given the "right" to do approvals for mailnews/* yet despite a few attempt at discussing, so hoping this can get triaged by next week!
Flags: needinfo?(mbanner)
Comment 19•11 years ago
|
||
Comment on attachment 686511 [details] [diff] [review] Like this? Yeah these should be fine, less risk of builds braking during release etc.
Attachment #686511 -
Flags: approval-comm-beta? → approval-comm-beta+
Flags: needinfo?(mbanner)
Updated•11 years ago
|
Attachment #696649 -
Flags: approval-comm-beta? → approval-comm-beta+
Comment 20•11 years ago
|
||
remote: https://hg.mozilla.org/releases/comm-beta/rev/123ca53cf6af remote: https://hg.mozilla.org/releases/comm-beta/rev/95425f5ca8a7
status-seamonkey2.16:
--- → fixed
status-thunderbird19:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•