Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Plain View
Accumulo >> mail # dev >> Re: Build failed in Jenkins: Accumulo-Trunk-Hadoop-2.0 #168


+
Billie Rinaldi 2013-04-02, 17:08
+
Christopher 2013-04-02, 21:24
+
Billie Rinaldi 2013-04-02, 21:32
Copy link to this message
-
Re: Build failed in Jenkins: Accumulo-Trunk-Hadoop-2.0 #168
"that is not the issue [here]" - Oh, sorry, I saw the timeout
exception and assumed...

--
Christopher L Tubbs II
http://gravatar.com/ctubbsii
On Tue, Apr 2, 2013 at 5:32 PM, Billie Rinaldi <[EMAIL PROTECTED]> wrote:
> On Tue, Apr 2, 2013 at 2:24 PM, Christopher <[EMAIL PROTECTED]> wrote:
>
>> We probably shouldn't have unit tests that fail because they run on a
>> slower computer than expected... unless we are explicitly testing
>> temporal behavior in that unit of code. Otherwise, we will continue to
>> get these false positive test failures when testing a unit of code
>> that works perfectly fine. If we're getting a failure because some
>> component of the code other than what we are explicitly testing in a
>> unit test is time-dependent, then that seems to me to be an indicator
>> that this is not a good unit test (but may be an essential
>> functional/integration test).
>>
>
> I agree that we should try to remove timing-based unit tests.  However,
> that is not the issue that was occurring with these servers.  They were
> failing all jobs with the same errors, not just ours.
>
> Billie
>
>
>
>>
>> --
>> Christopher L Tubbs II
>> http://gravatar.com/ctubbsii
>>
>>
>> On Tue, Apr 2, 2013 at 1:08 PM, Billie Rinaldi <[EMAIL PROTECTED]>
>> wrote:
>> > 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
>> >>
>>
+
David Medinets 2013-04-02, 21:32
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB