post-imaging setup on win32-slave04

RESOLVED FIXED

Status

Release Engineering
General
RESOLVED FIXED
7 years ago
4 years ago

People

(Reporter: jhford, Assigned: lsblakk)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

This has killed a bunch of build during a staging run.  Not sure what is wrong with this slave, but it looks like the build system can only find SDK version 5 but the build system is requiring version 6.
It was reimaged recently (bug 594040) and may be missing some files if the ref VM is out of date, or OPSI not set to install all the required packages.
I'll try to look at it this week.
Assignee: nobody → bhearsum
Noticed in a console that %LIB% is different between it and a working machine.

Working machine:
d:\sdks\v7.0\\lib;d:\msvs8\VC\ATLMFC\LIB;d:\msvs8\VC\LIB;d:\msvs8\VC\PlatformSDK\lib;d:\msvs8\SDK\v2.0\lib;;D:\mozilla-build\atlthunk_compat

This one:
C:\Program Files\Microsoft SDKs\Windows\v7.0\\lib;d:\msvs8\VC\ATLMFC\LIB;d:\msvs
8\VC\LIB;d:\msvs8\VC\PlatformSDK\lib;d:\msvs8\SDK\v2.0\lib;;D:\mozilla-build\atlthunk_compat

So, it appears to be finding the wrong directory for the Windows 7 SDK for some reason. The strangest part is that c:\program files\Microsoft SDKs\Windows\v7.0 doesn't even exist.
Depends on: 602639
(In reply to comment #3)
> Noticed in a console that %LIB% is different between it and a working machine.
> 
> Working machine:
> d:\sdks\v7.0\\lib;d:\msvs8\VC\ATLMFC\LIB;d:\msvs8\VC\LIB;d:\msvs8\VC\PlatformSDK\lib;d:\msvs8\SDK\v2.0\lib;;D:\mozilla-build\atlthunk_compat
> 
> This one:
> C:\Program Files\Microsoft
> SDKs\Windows\v7.0\\lib;d:\msvs8\VC\ATLMFC\LIB;d:\msvs
> 8\VC\LIB;d:\msvs8\VC\PlatformSDK\lib;d:\msvs8\SDK\v2.0\lib;;D:\mozilla-build\atlthunk_compat
> 
> So, it appears to be finding the wrong directory for the Windows 7 SDK for some
> reason. The strangest part is that c:\program files\Microsoft SDKs\Windows\v7.0
> doesn't even exist.

....and the ref platform has the correct LIB, so I'm pretty convinced that this was never re-imaged, or re-imaged incorrectly. I'm leaning towards the former, since khuey was the one using it, and it wouldn't shock me if he was playing with compilers, SDKs, or other such things.

Filed bug 602639 to re-image.
Doesn't look like I'll be getting to this while on buildduty
Assignee: bhearsum → nobody
Summary: mozilla-1.9.2 release builds don't work on moz2-win32-slave04 → post-imaging setup on win32-slave04
Whiteboard: [buildduty]
(Assignee)

Updated

7 years ago
Assignee: nobody → lsblakk
(Assignee)

Comment 6

7 years ago
tried to re-image this but ran into problems with opsi where it deinstall.cmd cannot run because it says that the OS isn't in the list of acceptable OSes to deinstall. the log shows that it thinks it's on windows NT instead of win2k3
(Assignee)

Comment 7

7 years ago
This machine is totally messed up and won't deinstall opsi, and also doesn't work with opsi client even when I re-installed opsi (as admin).  Requesting another re-image.
(Assignee)

Updated

7 years ago
Whiteboard: [buildduty]
(Assignee)

Comment 8

7 years ago
post-image steps done, machine syncs up with opsi and also has connected to staging-master.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.