river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Firmstone <j...@zeus.net.au>
Subject Re: Build failed in Hudson: River-trunk-QA #16
Date Sun, 12 Sep 2010 02:56:11 GMT
Ok,

I've now got an experimental build in skunk called pepe (Pepe Le Pew), I 
only experienced one test failure, 
com/sun/jini/test/spec/security/basicproxypreparer/Grant_Test.td, a 
NullPointerException, which has now been fixed.

Pepe should now pass all 581 running tests.

Significant points to note:

   1. Pepe contains no changes related to my CDC experimental changes
      (dropped, too much work), which I believe are responsible for the
      majority of failures experienced, this was due to insufficient
      test coverage during development, highlighting the importance
      ensuring we have all tests running, including investigating the
      remaining 21 that aren't being run.
   2. StreamServiceRegistrar related interfaces have been added and
      modified to extend ServiceRegistrar directly.
   3. Doesn't yet contain the TaskManager improvements.
   4. Doesn't yet contain Brian's SDM patch.
   5. Pepe contains the DynamicConcurrentPolicyProvider
   6. Pepe contains the experimental RevokeableDynamicPolicy
   7. Pepe contains Jonathan's build script improvements.
   8. Pepe contains recent qa additions made by Jonathan, see the
      commit's for details.
   9. I've used SVN copy from multiple trunk versions to retain
      important development evolution.

I'll add the changes in 3 & 4, then run the tests again.

Those two test failures below, I was able to repeat on my machine 
reliably, this might be due to it having 4 separate processor sockets, 
rather than being multicore.

Once I confirm the failures occurring in trunk are due to either 3&4 
above or the remaining experimental CDC code, we can take action 
cleaning up trunk and work on the new collaboration/merge development model.

If I deleted the current trunk version, can I then copy parts from 
earlier trunk revisions into trunk, without loosing the development 
evolution? 

If so, then I can keep Jonathan's recent improvements, with a known 
stable build without any experimental code.

Regards,

Peter.


Sim IJskes - QCG wrote:
> On 09-09-10 13:17, Sim IJskes - QCG wrote:
>>
>> And now (same setup):
>>
>
>      [java] # of tests started   = 581
>      [java] # of tests completed = 581
>      [java] # of tests skipped   = 21
>      [java] # of tests passed    = 579
>      [java] # of tests failed    = 2
>      [java]
>
>
>      [java] -----------------------------------------
>      [java] 
> com/sun/jini/test/spec/servicediscovery/lookup/LookupMinLessMax.td
>      [java] Test Failed: Test Failed: 
> com.sun.jini.qa.harness.TestException:  -- blocked longer than 
> expected -- requested block = 60 second(s), actual block
>  = 60 second(s)
>      [java]
>      [java] -----------------------------------------
>      [java] 
> com/sun/jini/test/spec/servicediscovery/lookup/LookupMinLessMaxFilter.td
>      [java] Test Failed: Test Failed: 
> com.sun.jini.qa.harness.TestException:  -- blocked longer than 
> expected -- requested block = 60 second(s), actual block
>  = 60 second(s)
>      [java]
>
>
>


Mime
View raw message