Windows 2003 X64 and Windows 7 X64

Kelly O'Hair kelly.ohair at oracle.com
Thu Oct 25 20:22:18 PDT 2012


I'm told that "Windows 2008" is Vista based, and "Windows 2008 R2" is Win7 based.
Can you check on the Windows 2008 system you used and verify if it is R2 or not? Thanks.

I asked Heikki  to spin up a Windows 2008 R2 VM, but if you have one already and have verified
it works there, that would be a  comforting thought.

My thinking was that we should move jdk8 builds to Win7 X64, but if "Windows 2008 R2" works, I'm willing
to change to "Windows 2008 R2". I was told that a server OS is easier to manage lab-wise.

-kto

On Oct 24, 2012, at 12:42 AM, Erik Joelsson wrote:

> My experience so far with OS versions is this:
> 
> My laptop (lenovo thinkpad 4 cores, maybe 2 years old) windows 7 x64, hangs frequently.
> Lab machine (HP Proliant DL360 G4p, 4 cores) windows 2003 ia32, hangs frequently
> Lab machine (older beta hardware, 16 cores) windows 2003 x64, no hangs in hudson (not using for manual runs)
> Lab machine (newer beta hardware, 64 cores) windows 2008 x64, no hangs in hudson or manual runs
> 
> Based on this small sample, and assuming 2008 and 7 are basically the same, I would say machine size is a bigger factor than OS version, but would need more data to say anything real I think.
> 
> /Erik
> 
> On 2012-10-23 19:18, Kelly O'Hair wrote:
>> I have been experimenting with using Windows 7 X64 for CYGWIN building rather than Windows 2003 X64.
>> 
>> I have no hard evidence yet, but it seems better. Anti-Virus conflict issues may  still be a problem.
>> 
>> It makes me think that maybe all this effort on Windows 2003 X64 build issues may be wasted, and maybe we
>> should consider just changing at least our 64bit builds to Windows 7 X64.
>> 
>> Both the old builds with MKS and the build-infra CYGWIN builds can work there with little to no change.
>> 
>> Thoughts?
>> 
>> -kto




More information about the build-infra-dev mailing list