Closed Bug 540672 Opened 16 years ago Closed 16 years ago

Tryserver builds won't run on XP since 18 Jan

Categories

(Testing :: General, defect)

1.9.2 Branch
x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: glennrp+bmo, Unassigned)

References

Details

My Tryserver builds for Windows XP (WINNT) are failing to run. After getting the usual "The Publisher could not be verified" window and selecting RUN I get a window that says Windows experiences an error and do I wish to send a bug report to Microsoft. My last good run was 17 Jan at 20;56 PST and the first failure was 18 Jan at 10:05 PST. Even a build where all I did was change a comment line fails. I see this behavior on both an XP-pro workstation and an XP laptop.
Forgot to say this is with 1.9.2
There seems to be more stuff wrong with the 1.9.2 repository. Besides the fact that the code fails to start on WinXP (still true as of 3PM EST Jan 19), there's this: Here's the Tryserver message, which essentially says all of the tests failed. Your Try Server unit test (baseline-1.9.2-Jan18) completed with warnings on win32. It should be available for download at http://build.mozilla.org/tryserver-builds/glennrp@gmail.com-baseline-1.9.2-Jan18 Summary of unittest results: check: <em class="testfail">T-FAIL</em> xpcshell-tests: 698/<em class="testfail">11</em> reftest: <em class="testfail">T-FAIL</em>&nbsp;<em class="testfail">L-FAIL</em> crashtest: <em class="testfail">T-FAIL</em>&nbsp;<em class="testfail">L-FAIL</em> mochitest-plain: <em class="testfail">T-FAIL</em>&nbsp;<em class="testfail">L-FAIL</em> mochitest-chrome: <em class="testfail">T-FAIL</em>&nbsp;<em class="testfail">L-FAIL</em> mochitest-browser-chrome: <em class="testfail">T-FAIL</em>&nbsp;<em class="testfail">L-FAIL</em> mochitest-a11y: <em class="testfail">T-FAIL</em>&nbsp;<em class="testfail">L-FAIL</em> Here is the patch, which only adds a couple of comment lines: diff -u8p -r -N -x '.mozconfig*' -x configure src-1.9.2/modules/libimg/png/MOZCHANGES src192/modules/libimg/png/MOZCHANGES --- src-1.9.2/modules/libimg/png/MOZCHANGES 2010-01-13 09:47:07.000000000 -0600 +++ src192/modules/libimg/png/MOZCHANGES 2010-01-18 13:02:16.000000000 -0600 @@ -1,11 +1,13 @@ Changes made to pristine png source by mozilla.org developers. +2010/01/18 -- Baseline 1.9.2 checkout + 2009/02/19 -- Synced with libpng-1.2.35 (bug #478901). 2008/08/21 -- Synced with libpng-1.2.31 (bug #418900). 2008/03/29 -- Initialize prev_row for each APNG frame, only when the frame size increases (bug #420416) 2008/01/18 -- Synced with libpng-1.2.24 (bug #408429).
WORKS FOR ME at 0825EST January 20.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Since no one else seems to have observed this bug, I think the best explanation for it is that there was some sort of pilot error on my part. Sorry for the noise.
You need to log in before you can comment on or make changes to this bug.