Hi all

Most of the recent builds timed out after one hour while building one
of the launchers.
In build 238 and 239 it was the full launcher.
In build 241 and 243 it was the stateless launcher.
Build 240 was successful and 242 stopped before building the launcher.

The logs always end with the statement

[JENKINS] Archiving
/home/hudson/hudson-slave/workspace/stanbol-trunk-1.6/trunk/launchers/stateless/target/org.apache.stanbol.launchers.stateless-0.9-SNAPSHOT.jar
to 
/home/hudson/hudson/jobs/stanbol-trunk-1.6/modules/org.apache.stanbol$org.apache.stanbol.launchers.stateless/builds/2011-06-26_15-03-01/archive/org.apache.stanbol/org.apache.stanbol.launchers.stateless/0.9-SNAPSHOT/org.apache.stanbol.launchers.stateless-0.9-SNAPSHOT.jar

in case of the stateless launcher or

[JENKINS] Archiving
/home/hudson/hudson-slave/workspace/stanbol-trunk-1.6/trunk/launchers/full/target/org.apache.stanbol.launchers.full-0.9-SNAPSHOT.jar
to 
/home/hudson/hudson/jobs/stanbol-trunk-1.6/modules/org.apache.stanbol$org.apache.stanbol.launchers.full/builds/2011-06-22_11-03-55/archive/org.apache.stanbol/org.apache.stanbol.launchers.full/0.9-SNAPSHOT/org.apache.stanbol.launchers.full-0.9-SNAPSHOT.jar

in case of the full launcher

For me that looks like there is some issue while copying the created
jars to some archive with the build artifacts. However I have no Idea
why this could case the timeout.

best
Rupert

-- 
| Rupert Westenthaler             [email protected]
| Bodenlehenstraße 11                             ++43-699-11108907
| A-5500 Bischofshofen

Reply via email to