river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Costers <jonathan.cost...@googlemail.com>
Subject Re: Build failed in Hudson: River-trunk-QA #16
Date Tue, 07 Sep 2010 10:33:12 GMT
You check out the trunk, set the property "run.tests" in your
<trunk>/build.properties to the tests that fail:

run.tests=com/sun/jini/test/spec/lookupdiscovery/MulticastMonitorAllChange.td

and from <trunk>/qa/build.xml, run the "run-tests" target.

This will only run the test you requested.

2010/9/7 Sim IJskes - QCG <sim@qcg.nl>

> On 09/07/2010 11:44 AM, Jonathan Costers wrote:
>
>> What I find really strange is that I have this one test failing on Hudson,
>> while it is passing on my machine ... (see my previous emails) I have a
>> freshly checked out trunk ... I'm suspecting a concurrency issue of some
>> sort.
>>
>
> That my idea exactly. Singlecore vs multicore could be very important here.
>
>
>  It would be very helpful if someone else could run this test locally and
>> post the results.
>>
>
> OK, i check out the trunk, and then? I only have 686 systems, multicore. I
> could boot an old Pentium 1 with a linux system. I can run 1 or 2 processor
> in vmware under linux.
>
> We can also try running a hudson slave, for a limited periode, and look how
> much it will affect operations here.
>
> What do you need?
>
> Gr. Sim
>

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