www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giridharan Kesavan <gkesa...@hortonworks.com>
Subject Re: jenkins flaky?
Date Mon, 25 Mar 2013 23:03:52 GMT
Im not sure on whats going on with the machine. I can try re-starting the
machine and may be spend sometime debugging this when the host comes back
online.

-Giri


On Mon, Mar 25, 2013 at 3:44 PM, Ted Dunning <ted.dunning@gmail.com> wrote:

> Is anybody else out there ?
>
> Any hints about what the problem is?
>
> On Mon, Mar 25, 2013 at 11:32 PM, Andy Seaborne <andy@apache.org> wrote:
>
> > On 24/03/13 06:28, Ted Dunning wrote:
> >
> >> I see a continuing pattern of jobs failing on Jenkins.  This happens
> with
> >> Mahout-Quality and Drill-Physical-Plan.  Both jobs are totally stable on
> >> other platforms and do not involve non-deterministic tests.  In any
> case,
> >> these failures can occur long before the tests even start.  Failures
> seem
> >> to occur for Mahout-Quality about 20% of all attempts.  There is also a
> >> lower rate issue in which the build times out after taking much longer
> >> than
> >> usual.
> >>
> >> The stack trace for the first kind of failure generally looks something
> >> like the trace below.
> >>
> >> Does anybody have any idea what is going on?
> >>
> >
> > We seen much the same with a common theme of the build slave being
> > "ubuntu2".
> >
> >         Andy
> >
> >
> >
> >> My feeling is that a build system that fails more often than the
> software
> >> being tested is just misleading and not worth much.
> >>
> >> hudson.util.IOException2: remote file operation failed:
> >> /home/hudson/hudson-slave/**workspace/Drill-Physical-Plan at
> >> hudson.remoting.Channel@**74114c2e:ubuntu2
> >>          at hudson.FilePath.act(FilePath.**java:861)
> >>          at hudson.FilePath.act(FilePath.**java:838)
> >>          at hudson.FilePath.toURI(**FilePath.java:966)
> >>          at hudson.tasks.MailSender.**createFailureMail(MailSender.**
> >> java:279)
> >>          at hudson.tasks.MailSender.**getMail(MailSender.java:154)
> >>          at hudson.tasks.MailSender.**execute(MailSender.java:100)
> >>          at hudson.maven.**MavenModuleSetBuild$**
> >> MavenModuleSetBuildExecution.
> >> cleanUp(MavenModuleSetBuild.**java:964)
> >>          at hudson.model.Run.execute(Run.**java:1613)
> >>          at hudson.maven.**MavenModuleSetBuild.run(
> >> MavenModuleSetBuild.java:477)
> >>          at hudson.model.**ResourceController.execute(
> >> ResourceController.java:88)
> >>          at hudson.model.Executor.run(**Executor.java:236)
> >> Caused by: hudson.remoting.**ChannelClosedException: channel is already
> >> closed
> >>          at hudson.remoting.Channel.send(**Channel.java:494)
> >>          at hudson.remoting.Request.call(**Request.java:129)
> >>          at hudson.remoting.Channel.call(**Channel.java:672)
> >>          at hudson.FilePath.act(FilePath.**java:854)
> >>          ... 10 more
> >> Caused by: hudson.remoting.Channel$**OrderlyShutdown
> >>          at hudson.remoting.Channel$**CloseCommand.execute(Channel.**
> >> java:850)
> >>          at hudson.remoting.Channel$2.**handle(Channel.java:435)
> >>          at hudson.remoting.**SynchronousCommandTransport$**
> >> ReaderThread.run(
> >> SynchronousCommandTransport.**java:60)
> >> Caused by: Command close created at
> >>          at hudson.remoting.Command.<init>**(Command.java:56)
> >>          at hudson.remoting.Channel$**CloseCommand.<init>(Channel.**
> >> java:844)
> >>          at hudson.remoting.Channel$**CloseCommand.<init>(Channel.**
> >> java:842)
> >>          at hudson.remoting.Channel.close(**Channel.java:909)
> >>          at hudson.remoting.Channel.close(**Channel.java:892)
> >>          at hudson.remoting.Channel$**CloseCommand.execute(Channel.**
> >> java:849)
> >>          ... 2 more
> >>
> >>
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message