I run the failed Math tests and got a litle bit strange results:
these 3 tests passed on the runtime built by DRLVM build and failed on
the runtime built by federated build. ie the command:
ant test -Dbuild.module=luni
-Dtest.jre.home=projects/trunk/working_vm/build/lnx_ia32_gcc_release/deploy/jdk/jre/
-Dtest.case=org.apache.harmony.luni.tests.java.lang.StrictMathTest

leads to the message:
   [junit] Tests run: 44, Failures: 1, Errors: 0, Time elapsed: 0.335 sec
   [junit] Test org.apache.harmony.luni.tests.java.lang.StrictMathTest FAILED

while command:
ant test -Dbuild.module=luni
-Dtest.jre.home=projects/drlvm/trunk/build/lnx_ia32_gcc_release/deploy/jdk/jre/
-Dtest.case=org.apache.harmony.luni.tests.java.lang.StrictMathTest

leads to the message:
   [junit] Running org.apache.harmony.luni.tests.java.lang.StrictMathTest
   [junit] Tests run: 44, Failures: 0, Errors: 0, Time elapsed: 0.332 sec

Both runtimes report one version:
svn = r550333, (Jun 26 2007), Linux/ia32/gcc 3.3.3, release build

Could someone from DRLVM-build gurus look at this issue?

thanks, Vladimir

On 6/26/07, Ivan Popov <[EMAIL PROTECTED]> wrote:
As I mentioned above, it is known failure, not a regression. It's safe
to add it to exclude list and ignore for now.

Thanks.
Ivan (jdwp person)

On 6/26/07, Tim Ellison <[EMAIL PROTECTED]> wrote:
> Stepan Mishura wrote:
> > On 6/26/07, Stepan Mishura wrote:
> >> On 6/25/07, Ivan Popov wrote:
> >> > I see two failures of jdktools tests, which are not new ones.
> >> >
> >>
> >> Ivan,
> >>
> >> Thanks for prompt failure analysis. I'm going to add HoldEventsTest to
> >> exclude list for intermittent failures on Linux, increase timeout and
> >> re-run tests.
> >
> > Ops, sorry ... I've updated the exclude list without getting agreement
> > from another committer. Please let me know if there any objections for
> > updating the exclude list.
>
> It would be good to hear from a VM/jdwp person whether this is a
> regression that needs to be fixed, or whether it is safe to ignore it
> for now.
>
> Regards,
> Tim
>

Reply via email to