On 2/15/07, Alexey Varlamov <[EMAIL PROTECTED]> wrote:
2007/2/15, Gregory Shimansky <[EMAIL PROTECTED]>:
> Vladimir Ivanov wrote:
> > Hello everyone,
> > I would like to discuss modes to run DRLVM jvmti, smoke and kernel tests.
> > Current state:
> > - jvmti: interpreter + default
> > - smoke: interpreter + default
> > - kernel: interpreter + jet + opt
> >
> > I suggest to add command line switch (one for all tests) to set modes.
> > In this case the default value will be:
> > - jvmti: interpreter + jet + opt
> > - smoke: interpreter + jet + opt
> > - kernel: interpreter + jet + opt
> >
> > Command line interface will be:
> > build.bat -Dtest.modes=jet,opt test
> >
> > Is it OK?
> > Issue HARMONY-3182 was created to track it.
>
> I think that in the light of the recent message by Xiao-Feng about GCv5
> we could also add a mode to test that GC. I am sure this will help its
> developers to improve its stability before we start to use it by default.

Nice idea! In fact this is already possible with kernel.test and
ehwa.test, like this:
$>build.bat kernel.test -Dkernel.test.mode=gcv5
-Dgcv5.switch="-XDvm.dlls=gcv5.dll"

When the issue 3182 will be integrated it also will be possible for
smoke and jvmti tests. The pattern of run was lent from kernel tests
:)

thanks, Vladimir


The default modes and cmd-line switches are set in
build/make/test.properties file.

--
Alexey

Reply via email to