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

Bug 327875

Summary:

Builds fail on slave1 not on slave2

Product:

Community

Reporter:

Steve Powell <zteve.powell>

Component:

CI-Jenkins

Assignee:

Eclipse Webmaster <webmaster>

Status:

CLOSED FIXED

QA Contact:

Severity:

normal

Priority:

CC:

glyn.normington

Version:

unspecified

Target Milestone:

---

Hardware:

OS:

Mac OS X - Carbon (unsup.)

Whiteboard:

Attachments:

Description	Flags
Diff between diagnostics on slave1 and slave2	none

Description Steve Powell

2010-10-15 06:52:48 EDT

E.g. Virgo.test.snapshot runs happily on slave2 but gives this error on slave1:

BUILD FAILED
/opt/users/hudsonbuild/workspace/virgo.test.snapshot/virgo-build/multi-bundle/artifact.xml:57: The following error occurred while executing this line:
/opt/users/hudsonbuild/workspace/virgo.test.snapshot/virgo-build/multi-bundle/common.xml:138: The following error occurred while executing this line:
/opt/users/hudsonbuild/workspace/virgo.test.snapshot/virgo-build/common/common.xml:150: Execute failed: java.io.IOException: Cannot run program "ant" (in directory "/opt/users/hudsonbuild/workspace/virgo.test.snapshot/org.eclipse.virgo.test.framework"): java.io.IOException: error=2, No such file or directory

which implies that the command "ant" fails to run.

This is probably because it is not in the path (normal ant commands are issued by hudson steps using an explicit path to the executable -- this is a command being executed explicitly).

Please check the set-up for slave1 and slave2 -- I expect the paths to be constructed similarly.  I am running ant 1.8.1 explicitly in this job.

Currently, the job disposition is "build2" which means I don't care which of slave1/2 it runs on.

Comment 1 Steve Powell

2010-10-15 09:46:06 EDT

Created attachment 180955 [details]
Diff between diagnostics on slave1 and slave2

The diff file shows, among other things, that the PATH environment variables and the java.library.path properties are different for the two slaves -- whereas the job spec is identical.

The PATH discrepancy accounts for this build problem.
Please can we match the execution environments as much as possible?

Comment 2 Eclipse Webmaster

2010-10-15 10:46:53 EDT

I've tweaked the path and run your test build without issue on slave1.

-M.

Comment 3 Steve Powell

2010-10-15 12:17:18 EDT

Thank you 

You appear to have modified the virgo.test.snapshot build configuration.

I shall be adjusting them all (virgo.*) back to build2.