Re: Build failed in Jenkins: mahout-nightly #737

No Joy (no time) yet. On Fri, Jan 6, 2012 at 6:59 AM, Grant Ingersoll wrote: > Any luck on this, as it is still failing for me on Ubuntu? > > We are slowing whittling down the 0.6 issues, but this one seems critical. > > > On Dec 31, 2011, at 8:07 PM, Ted Dunning wrote: > > > I have replicated t

Re: Build failed in Jenkins: mahout-nightly #737

Any luck on this, as it is still failing for me on Ubuntu? We are slowing whittling down the 0.6 issues, but this one seems critical. On Dec 31, 2011, at 8:07 PM, Ted Dunning wrote: > I have replicated this and applied this patch but the test still fails. > > I will take a longer look when I

Re: Build failed in Jenkins: mahout-nightly #737

I have replicated this and applied this patch but the test still fails. I will take a longer look when I get a chance. On Sat, Dec 31, 2011 at 3:57 PM, Ted Dunning wrote: > I just took a look and found several files not closed issues as Dmitriy > mentioned. There might be a buffering differenc

Re: Build failed in Jenkins: mahout-nightly #737

I just took a look and found several files not closed issues as Dmitriy mentioned. There might be a buffering difference on Linux versus make. I have a patch to fix this and will test right now on EC2 if I have enough time. On Sat, Dec 31, 2011 at 2:25 PM, Grant Ingersoll wrote: > Any progress

Re: Build failed in Jenkins: mahout-nightly #737

Any progress on this? Seems like it is a show stopper for code freeze. On Dec 29, 2011, at 3:58 AM, Dmitriy Lyubimov wrote: > note identical md5 for u200 and u400. > > On Thu, Dec 29, 2011 at 12:57 AM, Dmitriy Lyubimov wrote: >> MD5 sums >> >> b8217318a29ef69c58b921013eb019e5 /tmp/matrix85540

Re: Build failed in Jenkins: mahout-nightly #737

A-0 and A-400 match, and A-200 and A-600 match. Bs are all unique. U-200 matches U-400 On Thu, Dec 29, 2011 at 12:58 AM, Dmitriy Lyubimov wrote: > note identical md5 for u200 and u400. > > On Thu, Dec 29, 2011 at 12:57 AM, Dmitriy Lyubimov wrote: >> MD5 sums >> >> b8217318a29ef69c58b921013eb019e

Re: Build failed in Jenkins: mahout-nightly #737

note identical md5 for u200 and u400. On Thu, Dec 29, 2011 at 12:57 AM, Dmitriy Lyubimov wrote: > MD5 sums > > b8217318a29ef69c58b921013eb019e5  /tmp/matrix8554072597307396201/A-0 > 41db088ff74c5efd5b766dba253efc03  /tmp/matrix8554072597307396201/A-00200 > b8217318a29ef69c58b921013eb0

Re: Build failed in Jenkins: mahout-nightly #737

MD5 sums b8217318a29ef69c58b921013eb019e5 /tmp/matrix8554072597307396201/A-0 41db088ff74c5efd5b766dba253efc03 /tmp/matrix8554072597307396201/A-00200 b8217318a29ef69c58b921013eb019e5 /tmp/matrix8554072597307396201/A-00400 41db088ff74c5efd5b766dba253efc03 /tmp/matrix8554072597307

Re: Build failed in Jenkins: mahout-nightly #737

Thanks. Good hints. I will take a look on a linux machine in the next few days. On Thu, Dec 29, 2011 at 12:42 AM, Dmitriy Lyubimov wrote: > yes. i would venture to say that U computation (or restoration) is > somehow corrupted starting with 2nd block. at least it looks this way. > > On Thu, Dec

Re: Build failed in Jenkins: mahout-nightly #737

I see unclosed/unflushed streams in computeV, computeU, but that doesn't seem to be the reason. On Thu, Dec 29, 2011 at 12:42 AM, Dmitriy Lyubimov wrote: > yes. i would venture to say that U computation (or restoration) is > somehow corrupted starting with 2nd block. at least it looks this way. >

Re: Build failed in Jenkins: mahout-nightly #737

Does the same problem occur with another JVM, Dmitriy? JRockit or IBM's J9? Or even a different version of HotSpot? I remember we were once trying to figure out a similar bug (lots of computations, different result) in our code and it turned out that the problem was due to different native floating

Re: Build failed in Jenkins: mahout-nightly #737

yes. i would venture to say that U computation (or restoration) is somehow corrupted starting with 2nd block. at least it looks this way. On Thu, Dec 29, 2011 at 12:31 AM, Dmitriy Lyubimov wrote: > A-reconstructed difference looks good up to row 399 but starting at > row 400 differences do not ad

Re: Build failed in Jenkins: mahout-nightly #737

A-reconstructed difference looks good up to row 399 but starting at row 400 differences do not add up to 0 anymore (although both inputs are not 0). So it doesn't look like trivial case of something is not initialized on top of it. It does seem something to do with blocking mechanism though since

Re: Build failed in Jenkins: mahout-nightly #737

oh. it's because the synthetic input has only 4 singular values. On Wed, Dec 28, 2011 at 11:56 PM, Dmitriy Lyubimov wrote: > But it is not a problem reading U or V files, that's indeed what U and > V contain. > > On Wed, Dec 28, 2011 at 11:49 PM, Dmitriy Lyubimov wrote: >> U and V look suspect,

Re: Build failed in Jenkins: mahout-nightly #737

But it is not a problem reading U or V files, that's indeed what U and V contain. On Wed, Dec 28, 2011 at 11:49 PM, Dmitriy Lyubimov wrote: > U and V look suspect, degenerate (only 4 first columns are nonzero, > the rest of matrices are zeros. > > On Wed, Dec 28, 2011 at 11:44 PM, Dmitriy Lyubimo

Re: Build failed in Jenkins: mahout-nightly #737

U and V look suspect, degenerate (only 4 first columns are nonzero, the rest of matrices are zeros. On Wed, Dec 28, 2011 at 11:44 PM, Dmitriy Lyubimov wrote: > Yeah, fails for me on ubuntu without any special environment issues. > Which makes it easier, i can step thru. > > On Wed, Dec 28, 2011 a

Re: Build failed in Jenkins: mahout-nightly #737

Yeah, fails for me on ubuntu without any special environment issues. Which makes it easier, i can step thru. On Wed, Dec 28, 2011 at 9:01 PM, Ted Dunning wrote: > What do checksums look like? > > On Wed, Dec 28, 2011 at 6:33 PM, Grant Ingersoll wrote: > >> I commented out the deletion of the dir

Re: Build failed in Jenkins: mahout-nightly #737

What do checksums look like? On Wed, Dec 28, 2011 at 6:33 PM, Grant Ingersoll wrote: > I commented out the deletion of the dir in the tearDown. Not sure if that > looks reasonable or not, but on the surface they look equivalent. > > Here's the contents of the dir on Ubuntu: > -rw-rw-r-- 1 XX

Re: Build failed in Jenkins: mahout-nightly #737

I commented out the deletion of the dir in the tearDown. Not sure if that looks reasonable or not, but on the surface they look equivalent. Here's the contents of the dir on Ubuntu: -rw-rw-r-- 1 XX XX 1632612 2011-12-28 21:17 A-0 -rw-rw-r-- 1 XX XX 1632612 2011-12-28 21:1

Re: Build failed in Jenkins: mahout-nightly #737

Yeah.. but this is a difference from the correct answer. I am moderately sure that this is a problem writing to the temp directory. On Wed, Dec 28, 2011 at 3:45 PM, Grant Ingersoll wrote: > It's expecting the answer to be 0, but it's some really large value. > testSingularValues(org.apache.mahou

Re: Build failed in Jenkins: mahout-nightly #737

It's expecting the answer to be 0, but it's some really large value. testSingularValues(org.apache.mahout.math.ssvd.SequentialOutOfCoreSvdTest): expected:<0.0> but was:<4131200.37> On Dec 28, 2011, at 6:30 PM, Ted Dunning wrote: > I think that the answer is 0 because the model is not be

Re: Build failed in Jenkins: mahout-nightly #737

Fails on Ubuntu, but passes on my Mac. On Dec 28, 2011, at 6:21 PM, Grant Ingersoll wrote: > I can reproduce outside of Jenkins. It really seems odd that the answer is > off by so much. > > On Dec 28, 2011, at 2:15 AM, Dmitriy Lyubimov wrote: > >> I vaguely remember Jenkins had problems with

Re: Build failed in Jenkins: mahout-nightly #737

I think that the answer is 0 because the model is not being read and we are swallowing an exception somewhere. This is what an uninitialized matrix would give as a result. On Wed, Dec 28, 2011 at 3:21 PM, Grant Ingersoll wrote: > I can reproduce outside of Jenkins. It really seems odd that the

Re: Build failed in Jenkins: mahout-nightly #737

I can reproduce outside of Jenkins. It really seems odd that the answer is off by so much. On Dec 28, 2011, at 2:15 AM, Dmitriy Lyubimov wrote: > I vaguely remember Jenkins had problems with creating stuff in Java tmp > dir. E.g. I remember that was creating problems for Mr tasks in local mr >

RE: Build failed in Jenkins: mahout-nightly #737

> -Original Message- > From: Jeff Eastman [mailto:j...@windwardsolutions.com] > Sent: Wednesday, 28 December 2011 3:31 PM > To: dev@mahout.apache.org; infrastruct...@apache.org > Subject: Re: Build failed in Jenkins: mahout-nightly #737 > > +infra@ All build relate

Re: Build failed in Jenkins: mahout-nightly #737

I'm seeing this pretty consistently on my Jenkins locally, but then when I run on my Mac, it passes. On Dec 27, 2011, at 10:34 PM, Jeff Eastman wrote: > I'm getting a lot of these emails yet all the tests run locally for me. Does > anybody have an idea what the problem is? This close to a relea

Re: Build failed in Jenkins: mahout-nightly #737

I vaguely remember Jenkins had problems with creating stuff in Java tmp dir. E.g. I remember that was creating problems for Mr tasks in local mr mode legitimately using boxed task temporary space. OK I'll try to scan for the problem tomorrow. On Dec 27, 2011 10:50 PM, "Ted Dunning" wrote: > So I

Re: Build failed in Jenkins: mahout-nightly #737

So I am like everybody else. The test works for me. My suspicion is that there is something going on with the temporary directory that I am trying to use and that the environment that Jenkins is using is somehow strange. The only slightly surprising idiom I am using is to create a temporary file

Re: Build failed in Jenkins: mahout-nightly #737

Indeed it does. Thanks for pointing that out. This error is very strange. On Tue, Dec 27, 2011 at 10:06 PM, Dmitriy Lyubimov wrote: > Ted, > > do you have an idea why this test may be failing? I think this test comes > with M-792 commit. > > I can take a look at it, I suspect something in the

Re: Build failed in Jenkins: mahout-nightly #737

Ted, do you have an idea why this test may be failing? I think this test comes with M-792 commit. I can take a look at it, I suspect something in the environment can be tripping it. On Dec 27, 2011 8:54 PM, "Sean Owen" wrote: > It's all errors in the Apache infrastructure, rather than a real te

Re: Build failed in Jenkins: mahout-nightly #737

+infra@ Well, yes, I guess everybody is ignoring them. But that kinda begs the question of why we even bother to have Jenkins if we are going to always ignore its warnings? I'm a big fan of continuous integration and I've managed its administration before so I understand the challenges. But t

Re: Build failed in Jenkins: mahout-nightly #737

It's all errors in the Apache infrastructure, rather than a real test failure. At least, stuff passes for me locally, and that's what's important. So I'm ignoring these. On Tue, Dec 27, 2011 at 9:34 PM, Jeff Eastman wrote: > I'm getting a lot of these emails yet all the tests run locally for me.

Re: Build failed in Jenkins: mahout-nightly #737

I'm getting a lot of these emails yet all the tests run locally for me. Does anybody have an idea what the problem is? This close to a release it would be really nice to have Jenkins on our side. Jeff On 12/27/11 4:54 PM, Apache Jenkins Server wrote: See