http://tinderbox.mozilla.org/showbuilds.cgi?tree=SeaMonkey&maxdate=1261230389&hours=24&legend=0&norules=1 moz:d303e54445e7 was fine. moz:eeba84d24038 went red because of bug 524944 landing. moz:f6f1982d758d fixed that bustage. But this bug appeared. Firefox, Thunderbird and 'WINNT 5.2 comm-central-trunk nightly' are green. Maybe a stuck file/process? Or this tree needs a clobber? ...
This must be a code failure - it happens on all machines, and actually started right _after_ I clobbered dist/ on them.
And here's a good hint of what's up there - an error message shown on 3 of the 4 machines: shlibsign.exe - Unable To Locate Component The application has failed to start because sqlite3.dll was not found. Re-installing the application may fix this problem.
Sounds to me like something else caused by bug 513747 but maybe hidden until we clobbered dist/ on the machines. I completely clobbered objdir on the machines to be sure, but I think very much that this is related to the sqlite renaming.
["Mid-air collision detected!", posting anyway, ftr.] (In reply to comment #0) Regression timeframe: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=d303e54445e7&tochange=f6f1982d758d Nothing obvious to me. (but see below) (In reply to comment #1) > This must be a code failure - it happens on all machines, and actually started > right _after_ I clobbered dist/ on them. (Well, I couldn't guess that, as it's not noted on the waterfall...) Maybe the clobber triggered this failure somehow: if it's a code issue, it might be from an older changeset :-/
(In reply to comment #3) > Sounds to me like something else caused by bug 513747 but maybe hidden until we > clobbered dist/ on the machines. Maybe, yes. It even looks like it could be related to bug 519550... > I completely clobbered objdir on the machines to be sure, but I think very much > that this is related to the sqlite renaming. Worth trying, though I wonder why it fails on this tree only and nowhere else :-< (I mean, at least Firefox does automatic clobber, doesn't it?)
Looks like the complete clobber of the objdir helped in the end, all machines came back green after all - and yes, I vaguely remember that Firefox needed a clobber there as well - I guess the Windows build chain has a problem finding out about changed dependencies...
Yeah, both bugs were pushed with a clobber: see bug 513747 comment 87 for example. V.Fixed, per tinderbox.