:-)) now that is way more important. Have fun! Sure, I'll run some more tests tonight.
2010/8/30 Patricia Shanahan <[email protected]> > 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 >
