Well, my scenario is to make sure that my fixes in beans don't introduce new hangs/failures on DRLVM. This means running AWT and SWING tests on top of DRLVM that was a painful process before.
Regards, 2006/11/9, Vladimir Ivanov <[EMAIL PROTECTED]>:
On 11/9/06, Alexei Zakharov <[EMAIL PROTECTED]> wrote: > > So the best practice to run classlib tests on DRLVM is now: > ant -Dhy.test.mode="perTest" [-Dbuild.module=blah-blah] test > ? Actually, it depends on your choice :) The mode -Dhy.test.forkmode=perTestwill be useful: - to identify crashed/ hang up tests - to run tests under CC But of cause we should work to pass all tests on DRLVM in the default mode (-Dhy.test.forkmode=once). Thanks, Vladimir > Regards, > > 2006/11/9, Alexey Petrenko <[EMAIL PROTECTED]>: > > I'll take a look. > > > > SY, Alexey > > > > 2006/11/9, Vladimir Ivanov <[EMAIL PROTECTED]>: > > > Hello committers, > > > > > > could somebody take care about > > > *HARMONY-2107*<http://issues.apache.org/jira/browse/HARMONY-2107>? > > > > > > It is trivial to fix issue allows easily identify tests that leads to > vm > > > hang up/crash in the process of enabling classlib tests over VM.
-- Alexei Zakharov, Intel Enterprise Solutions Software Division
