We had a runtime bustage today that strangely wasn't picked up by any of the tinderboxes. I'd expected xpcshell-tests to pick it up, but they may have just got away with it. What I did realise was that the bloat boxes are building fully-shared builds. They can't do full-static builds at the moment because mac fails with a build error, but I'd at least like to add --enable-static-mail to the build options. The option builds mailnews as two dlls (one for most of mailnews, the other for import) and as a result uses slight different code. If we had had this specified, we'd have had a chance of picking up the runtime bustage because we'd have been hitting the appropriate code. The non-static mail option is really only maintained for developers, so lets switch this and get the code a bit nearer to what we actually release.
Created attachment 385727 [details] [diff] [review] The fix This adds --enable-static-mail to all the bloat mozconfigs. I've also made debug/optimise be consistently ordered across the files. Probably best also to clobber when we check this due to the changes from multiple to a few dlls.
Comment on attachment 385727 [details] [diff] [review] The fix This is fine, and doesn't require a buildbot reconfiguration. Just land this and the next set of bloat builds will pick up the new mozconfigs.
Landed and clobbered builds: http://hg.mozilla.org/build/buildbot-configs/rev/3a576e4435da Currently waiting for them to cycle.
This was fixed a while ago.