You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by Vladimir Ivanov <iv...@gmail.com> on 2007/01/30 13:33:17 UTC

[drlvm][pre-integration testing] is it OK to skip 'interpreter' mode in pre-integration testing?

Hello everyone,

now the 'build.bat test' target for DRLVM include run of jvmti, smoke and
kernel tests in different modes. The slowest one is interpreter. My question
is: may we exclude this mode from the pre-integration testing and add the
run of regression suite instead of it? It reduces the pre-integration
testing time from ~1 hour up to ~15 minutes. Is it critical? Can we just add
new tests to the 'test' target?  Of cause, CC runs of DRLVM tests should
include all modes of runs to detect regression.


 thanks, Vladimir

Re: [drlvm][pre-integration testing] is it OK to skip 'interpreter' mode in pre-integration testing?

Posted by Vladimir Ivanov <iv...@gmail.com>.
On 1/30/07, Geir Magnusson Jr. <ge...@pobox.com> wrote:
>
> On Jan 30, 2007, at 12:33 PM, Vladimir Ivanov wrote:
>
> > Hello everyone,
> >
> > now the 'build.bat test' target for DRLVM include run of jvmti,
> > smoke and
> > kernel tests in different modes. The slowest one is interpreter. My
> > question
> > is: may we exclude this mode from the pre-integration testing and
> > add the
> > run of regression suite instead of it? It reduces the pre-integration
> > testing time from ~1 hour up to ~15 minutes. Is it critical? Can we
> > just add
> > new tests to the 'test' target?  Of cause, CC runs of DRLVM tests
> > should
> > include all modes of runs to detect regression.
>
> Any chance of parameterizing?  Like default is all, or specify a
> list...?

Yes. I think this should be managed by command line options.
 thanks, Vladimir
>
> geir
>
> >
> >
> > thanks, Vladimir
>
>

Re: [drlvm][pre-integration testing] is it OK to skip 'interpreter' mode in pre-integration testing?

Posted by "Geir Magnusson Jr." <ge...@pobox.com>.
On Jan 30, 2007, at 12:33 PM, Vladimir Ivanov wrote:

> Hello everyone,
>
> now the 'build.bat test' target for DRLVM include run of jvmti,  
> smoke and
> kernel tests in different modes. The slowest one is interpreter. My  
> question
> is: may we exclude this mode from the pre-integration testing and  
> add the
> run of regression suite instead of it? It reduces the pre-integration
> testing time from ~1 hour up to ~15 minutes. Is it critical? Can we  
> just add
> new tests to the 'test' target?  Of cause, CC runs of DRLVM tests  
> should
> include all modes of runs to detect regression.

Any chance of parameterizing?  Like default is all, or specify a  
list...?

geir

>
>
> thanks, Vladimir