I looked at the console output but can't see what is wrong. My change
was only to a README file. I changed "two" to "too". How can that go
wrong?

On Mon, Jul 30, 2012 at 8:30 PM, Apache Jenkins Server
<[EMAIL PROTECTED]> wrote:
> See <https://builds.apache.org/job/Accumulo-Trunk/436/changes>
>
> Changes:
>
> [medined] ACCUMULO-707 - README typo

I doubt it had anything to do with your change.  At the end of the
message it says something about the build timing out.  Maybe its an
issue w/ infrastructure, like an NFS server down, network issue, etc?

On Mon, Jul 30, 2012 at 8:40 PM, David Medinets
<[EMAIL PROTECTED]> wrote:
> I looked at the console output but can't see what is wrong. My change
> was only to a README file. I changed "two" to "too". How can that go
> wrong?
>
> On Mon, Jul 30, 2012 at 8:30 PM, Apache Jenkins Server
> <[EMAIL PROTECTED]> wrote:
>> See <https://builds.apache.org/job/Accumulo-Trunk/436/changes>
>>
>> Changes:
>>
>> [medined] ACCUMULO-707 - README typo

Will it automatically attempt a rebuild? Or can we try a build manually?

On Tue, Jul 31, 2012 at 11:17 AM, Keith Turner <[EMAIL PROTECTED]> wrote:
> I doubt it had anything to do with your change.  At the end of the
> message it says something about the build timing out.  Maybe its an
> issue w/ infrastructure, like an NFS server down, network issue, etc?
>
> On Mon, Jul 30, 2012 at 8:40 PM, David Medinets
> <[EMAIL PROTECTED]> wrote:
>> I looked at the console output but can't see what is wrong. My change
>> was only to a README file. I changed "two" to "too". How can that go
>> wrong?
>>
>> On Mon, Jul 30, 2012 at 8:30 PM, Apache Jenkins Server
>> <[EMAIL PROTECTED]> wrote:
>>> See <https://builds.apache.org/job/Accumulo-Trunk/436/changes>
>>>
>>> Changes:
>>>
>>> [medined] ACCUMULO-707 - README typo

Looks like our builds are failing on ubuntu5.  I've excluded it from our
builds for now.  ubuntu2, which I removed for the same reason (same error)
a few weeks ago, may be working again so I'm experimentally adding it back
in.

Billie
On Tue, Apr 2, 2013 at 8:02 AM, Apache Jenkins Server <
[EMAIL PROTECTED]> wrote:

> See <https://builds.apache.org/job/Accumulo-Trunk-Hadoop-2.0/168/>
>
> ------------------------------------------
> Failed to access build log
>
> hudson.util.IOException2: remote file operation failed:
> /home/jenkins/jenkins-slave/workspace/Accumulo-Trunk-Hadoop-2.0 at
> hudson.remoting.Channel@ea84c1e:ubuntu5
>         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: java.io.IOException
>         at hudson.remoting.Channel.close(Channel.java:910)
>         at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:110)
>         at hudson.remoting.PingThread.ping(PingThread.java:120)
>         at hudson.remoting.PingThread.run(PingThread.java:81)
> Caused by: java.util.concurrent.TimeoutException: Ping started on
> 1364900366871 hasn't completed at 1364900606872
>         ... 2 more
>