Mailing-List: contact river-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: river-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of pats@acm.org designates
 209.86.89.61 as permitted sender)
Message-ID: <4C7BC292.1040905@acm.org>
Date: Mon, 30 Aug 2010 07:39:14 -0700
From: Patricia Shanahan <pats@acm.org>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: river-dev@incubator.apache.org
Subject: Re: Build failed in Hudson: River-trunk-QA #3
References: <1441997136.1281283129487143.JavaMail.hudson@aegis>
	<1102011184.1621283168954440.JavaMail.hudson@aegis>
 <AANLkTinJLbCyGz6ZvqufJc_4Rh+MC=WCPV8qPoRNtjx2@mail.gmail.com>
In-Reply-To: <AANLkTinJLbCyGz6ZvqufJc_4Rh+MC=WCPV8qPoRNtjx2@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Jonathan Costers wrote:
> OK, this one is ligitimate ...
> 
> The changes that were committed yesterday apparently cause a single QA test
> to fail:
> 
> [java] com/sun/jini/test/spec/
> lookupdiscovery/MulticastMonitorAllChange.td
>     [java] Test Failed: Test Failed: com.sun.jini.qa.harness.TestException:
> change failed -- waited 870 seconds (14 minutes) -- 3 change event(s)
> expected, 0 change event(s) received
> 
> Note that this QA run did not include "servicediscovery" nor any other new
> test categories.
> The same tests were run as were run when the QA run (build #1) passed
> yesterday.
> 
> Any chance this can get some more attention?
> IMHO, getting this fixed is our top priority right now.
> 

I agree with the priority within River, but I am spending the next few 
hours on something even higher priority - going ceramic painting with a 
friend. I'll check the mailing list when I get back. If nothing else 
happens, I'll look into it this afternoon or evening.

If you have time, could you check whether it is a solid failure or 
intermittent?

Patricia