Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 316930

Summary:	please install Sun x86_64 VMs on in /shared/common to be used on build2
Product:	Community	Reporter:	Kim Moir <kim.moir>
Component:	CI-Jenkins	Assignee:	CI Admin Inbox <ci.admin-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	d_a_carver
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Kim Moir

2010-06-15 11:35:01 EDT

I've been testing the new hudson slave, build2 and have been running into a vm issue.  See

https://bugs.eclipse.org/bugs/show_bug.cgi?id=312597#c24

Could you install the Sun versions of the x86_64 vms in shared common 
so I can see if this resolves the issue.  I think the ones we need are

Sun 5 update 22 for x86_64
Sun 6 update 20 for x86_64

Comment 1 David Carver

2010-06-15 15:11:30 EDT

(In reply to comment #0)
> I've been testing the new hudson slave, build2 and have been running into a vm
> issue.  See
> 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=312597#c24
> 
> Could you install the Sun versions of the x86_64 vms in shared common 
> so I can see if this resolves the issue.  I think the ones we need are
> 
> Sun 5 update 22 for x86_64
> Sun 6 update 20 for x86_64

Sun JDK 5 update 22 is already in:

/shared/common/jdk-1.5.0-22.x86_64

And Java 6 should be:

/shared/common/jdk-1.6.x86_64

If you set your Job to use Base Java 5.0, or Base Java 6.0 installation, it should pick these up when running on build 2.  The JDK installations for the build2 node are configured for the particular server.

Comment 2 Kim Moir

2010-06-15 15:24:46 EDT

Sorry, I typed java -version in these directories instead of ./java version so I thought that they were IBM vms when they were in fact Sun VMs. The default java on build2 points to an IBM vm.  So guess I'll have to try launching the build with a 1.5 vm and see if this avoids the vm bug.

Comment 3 David Carver

2010-06-15 15:49:20 EDT

(In reply to comment #2)
> Sorry, I typed java -version in these directories instead of ./java version so
> I thought that they were IBM vms when they were in fact Sun VMs. The default
> java on build2 points to an IBM vm.  So guess I'll have to try launching the
> build with a 1.5 vm and see if this avoids the vm bug.

If you follow:

https://build.eclipse.org/hudson/computer/build2/configure

after logging in, you'll see the various configurations for build2.   

Both Java 5.0 Base and Java 6.0 Base point to the correct installation.  As you noted you'll need to specify the JDK to use in your Hudson Job configuration to make sure it uses that JDK.

Comment 4 Denis Roy

2010-08-16 10:42:57 EDT

Since 'build2' doesn't really exist anymore as a Hudson slave, I'll close this.