Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 337283 - virgo.kernel.snapshot build is unstable on hudson-slave2 and is OK on hudson-slave1
Summary: virgo.kernel.snapshot build is unstable on hudson-slave2 and is OK on hudson-...
Status: CLOSED WORKSFORME
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: CI-Jenkins (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Webmaster CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-16 03:23 EST by violeta.georgieva CLA
Modified: 2011-02-17 06:59 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description violeta.georgieva CLA 2011-02-16 03:23:56 EST
Build Identifier: 

Hello,

We have problems with virgo.kernel.snapshot job when it is executed on hudson-slave2.

The tests failed with

Caused by: java.io.FileNotFoundException: /opt/users/hudsonbuild/workspace/virgo.kernel.snapshot/org.eclipse.virgo.kernel.smoketest/target/test-expanded/virgo-kernel-3.0.0.CI-2011-02-09_08-01-37/config/org.eclipse.virgo.kernel.users.properties (No such file or directory)

The file is existing in the workspace.

When I change the build to be run on hudson-slave1 then the build and the tests are successfully executed. Unfortunately when building on hudson-slave1 we experience the problem described in bug 334069.

Could you please check what's going on?

Thanks in advance
Regards
Violeta


Reproducible: Always
Comment 1 Eclipse Webmaster CLA 2011-02-16 09:57:12 EST
Based on this line in your log:

 [junit] Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 9875; nested exception is: 
    [junit] 	java.net.BindException: Address already in use

I went digging on slave2 and found the following process:

55011    22585     1  0 Feb09 ?        00:05:46 /opt/public/common/sun-jdk1.6.0_21_x64/jre/bin/java -Dcom.sun.management.jmxremote.port=9875 -Dcom.sun.management.jmxremote.authenticate=true -Dcom.sun.management.jmxremote.login.config=virgo-kernel -Dcom.sun.management.jmxremote.access.file=/opt/users/hudsonbuild/workspace/virgo.kernel.snapshot/org.eclipse.virgo.kernel.smoketest/target/test-expanded/virgo-kernel-3.0.0.CI-2011-02-09_08-01-37/config/org.eclipse.virgo.kernel.jmxremote.access.properties -Djavax.net.ssl.keyStore=/opt/users/hudsonbuild/workspace/virgo.kernel.snapshot/org.eclipse.virgo.kernel.smoketest/target/test-expanded/virgo-kernel-3.0.0.CI-2011-02-09_08-01-37/config/keystore (snip)

So I suspect that one of your previous builds started this process, and then failed to kill it, and so it's been blocking runs on that slave.

I've killed the job so let me know if the problem persists.

This is the first job I've ever seen with a parameter list so long that ps -aef can't display it all.

-M.
Comment 2 violeta.georgieva CLA 2011-02-17 06:59:24 EST
Thanks!