Closed Bug 424159 Opened 16 years ago Closed 16 years ago

win32 unit test machines need new SDK

Categories

(Release Engineering :: General, defect, P2)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: rcampbell)

References

Details

Attachments

(1 file)

I was told there was a patch landed last night that worked fine on the try server and blew up on the unit test machines because they don't have the new SDK on them. We upgraded the Build machines a couple months ago but I guess these were missed because they weren't on our radar :(.

Here's the instructions we followed when upgrading the build machines:
http://wiki.mozilla.org/ReferencePlatforms/Win32#Install_Microsoft.C2.AE_Windows.C2.AE_Software_Development_Kit_Update_for_Windows_Vista

INCLUDE and LIB will need to be adjusted to have the new SDK first. You should also set SDKDIR should also be set. Here's what the try server uses, for what it's worth: http://mxr.mozilla.org/mozilla/source/tools/buildbotcustom/env.py
Blocks: 412374
Flags: blocking1.9?
wasn't only the Firefox win32 unit test machines... other machines busted by this patch:
fxdbug-win32-tb -- http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1205993760.1205995347.14436.gz
sea-win32-tbox -- http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1205994660.1205997272.18666.gz

These both went green after the patch was backed out.
Two problems now actually, those are different. I'm going to have to modify the patch to use getprocaddress on the event calls I'm using. The build problem though is still present because we'll need the headers. (I could define this stuff manually in the code, but we shouldn't have too if the sdk is to date.)
Flags: blocking1.9? → blocking1.9+
Priority: -- → P1
I'm going to schedule some down-time to get this installed on qm-win2k3-01 early Monday morning.
Assignee: nobody → rcampbell
Whiteboard: need downtime Monday, Mar 24, 2008 for installation
Should this really block the beta?  It's marked as a P1.  Getting this monday is sorta late, right?
Doesn't block beta, no, as the bug which requires this doesn't block beta. If this turns out to also block bug 416683, though, it will block beta.

Jim: does bug 4166183 depend on this?
Priority: P1 → P2
Nope, unrelated. This is tied to new apis for parental controls related stuff in vista, bug 416683 is tied to the virus scanning we added a little while back. 
QA Contact: build → release
These are installed but not currently referenced in the buildbot configs. Not sure we need to add the include, libs and sdk directories to the path or not.
Whiteboard: need downtime Monday, Mar 24, 2008 for installation → add paths to configurations
path additions for mozbuild unittest box
Attachment #311430 - Flags: review?(ccooper)
Attachment #311430 - Flags: review?(ccooper) → review+
Checking in mozbuild.py;
/cvsroot/mozilla/tools/buildbot-configs/testing/unittest/mozbuild.py,v  <--  mozbuild.py
new revision: 1.16; previous revision: 1.15
done
applied to master
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Whiteboard: add paths to configurations
Component: Release Engineering: Talos → Release Engineering
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: