You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@apache.org by "Kevin A. McGrail" <KM...@PCCC.com> on 2013/01/11 19:45:18 UTC
Fwd: Build failed in Jenkins: SpamAssassin-trunk #8309
I believe solaris1 from jenkins is low on diskspace and this might be a
known issue...
-------- Original Message --------
Subject: Build failed in Jenkins: SpamAssassin-trunk #8309
Date: Fri, 11 Jan 2013 18:20:57 +0000 (UTC)
From: Apache Jenkins Server <je...@builds.apache.org>
To: dev@spamassassin.apache.org
See <https://builds.apache.org/job/SpamAssassin-trunk/8309/changes>
Changes:
[kmcgrail] small update for dkim test rename
[kmcgrail] Prep for 3.4.0-pre2
[kmcgrail] Switch to handling of Version in redis.pm - bug 6888
[kmcgrail] replacing dkim test with dkim2
[kmcgrail] removing dkim.t because test is replaced by dkim2.t
[kmcgrail] Small cleanup that EX_TOOBIG is never used for spamd per bug 5412
------------------------------------------
Started by an SCM change
Building remotely on solaris1 in workspace <https://builds.apache.org/job/SpamAssassin-trunk/ws/>
Updating http://svn.apache.org/repos/asf/spamassassin/trunk
U lib/Mail/SpamAssassin/BayesStore/Redis.pm
U MANIFEST
D xt/50_dkim2.t
U build/README
U spamc/spamc.pod
D t/dkim2.t
D t/dkim.t
A t/dkim.t
At revision 1432199
[locks-and-latches] Checking to see if we really have the locks
[locks-and-latches] Have all the locks, build can start
[SpamAssassin-trunk] $ /bin/bash -xe /var/tmp/hudson5214043703259009961.sh
FATAL: command execution failed
java.io.IOException: Not enough space
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.<init>(UNIXProcess.java:53)
at java.lang.ProcessImpl.start(ProcessImpl.java:65)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at hudson.Proc$LocalProc.<init>(Proc.java:244)
at hudson.Proc$LocalProc.<init>(Proc.java:216)
at hudson.Launcher$LocalLauncher.launch(Launcher.java:763)
at hudson.Launcher$ProcStarter.start(Launcher.java:353)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:988)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:955)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:595)
Build step 'Execute shell' marked build as failure
[locks-and-latches] Releasing all the locks
[locks-and-latches] All the locks released
Archiving artifacts
Recording test results
RE: Build failed in Jenkins: SpamAssassin-trunk #8309
Posted by Gavin McDonald <ga...@16degrees.com.au>.
> -----Original Message-----
> From: Kevin A. McGrail [mailto:KMcGrail@PCCC.com]
> Sent: Saturday, 12 January 2013 5:15 AM
> To: builds@apache.org
> Subject: Fwd: Build failed in Jenkins: SpamAssassin-trunk #8309
>
> I believe solaris1 from jenkins is low on diskspace and this might be a known
> issue...
It’s a /tmp space issue.
Disk space has over 160GB free.
/tmp space has 150MB left.
cleared. (until next time)
Gav...
>
>
>
> -------- Original Message --------
> Subject: Build failed in Jenkins: SpamAssassin-trunk #8309
> Date: Fri, 11 Jan 2013 18:20:57 +0000 (UTC)
> From: Apache Jenkins Server <je...@builds.apache.org>
> To: dev@spamassassin.apache.org
>
>
>
> See <https://builds.apache.org/job/SpamAssassin-trunk/8309/changes>
>
> Changes:
>
> [kmcgrail] small update for dkim test rename
>
> [kmcgrail] Prep for 3.4.0-pre2
>
> [kmcgrail] Switch to handling of Version in redis.pm - bug 6888
>
> [kmcgrail] replacing dkim test with dkim2
>
> [kmcgrail] removing dkim.t because test is replaced by dkim2.t
>
> [kmcgrail] Small cleanup that EX_TOOBIG is never used for spamd per bug
> 5412
>
> ------------------------------------------
> Started by an SCM change
> Building remotely on solaris1 in workspace
> <https://builds.apache.org/job/SpamAssassin-trunk/ws/>
> Updating http://svn.apache.org/repos/asf/spamassassin/trunk
> U lib/Mail/SpamAssassin/BayesStore/Redis.pm
> U MANIFEST
> D xt/50_dkim2.t
> U build/README
> U spamc/spamc.pod
> D t/dkim2.t
> D t/dkim.t
> A t/dkim.t
> At revision 1432199
> [locks-and-latches] Checking to see if we really have the locks
> [locks-and-latches] Have all the locks, build can start
> [SpamAssassin-trunk] $ /bin/bash -xe
> /var/tmp/hudson5214043703259009961.sh
> FATAL: command execution failed
> java.io.IOException: Not enough space
> at java.lang.UNIXProcess.forkAndExec(Native Method)
> at java.lang.UNIXProcess.<init>(UNIXProcess.java:53)
> at java.lang.ProcessImpl.start(ProcessImpl.java:65)
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
> at hudson.Proc$LocalProc.<init>(Proc.java:244)
> at hudson.Proc$LocalProc.<init>(Proc.java:216)
> at hudson.Launcher$LocalLauncher.launch(Launcher.java:763)
> at hudson.Launcher$ProcStarter.start(Launcher.java:353)
> at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:988)
> at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:955)
> at hudson.remoting.UserRequest.perform(UserRequest.java:118)
> at hudson.remoting.UserRequest.perform(UserRequest.java:48)
> at hudson.remoting.Request$2.run(Request.java:326)
> at
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorSe
> rvice.java:72)
> at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
> at java.util.concurrent.FutureTask.run(FutureTask.java:123)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecut
> or.java:651)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.ja
> va:676)
> at java.lang.Thread.run(Thread.java:595)
> Build step 'Execute shell' marked build as failure
> [locks-and-latches] Releasing all the locks
> [locks-and-latches] All the locks released
> Archiving artifacts
> Recording test results
>
>