You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by Stepan Mishura <st...@gmail.com> on 2008/02/22 06:13:17 UTC
[testing] second M5 candidate (r629320) testing status.
Hi all,
Here is r629320 snapshot testing status. Briefly, there are several
failures: some of them are intermittent and/or known issues (i.e there
is JIRA for tracking). Also there are several new regressions for
investigation if they are blockers for M5 or not. I think that the
most serious one is a crash of Dacapo on Linux'es. Could anyone to
look into?
Please add your comments and clarifications.
1) Classlib:
5 failures in text module because of HARMONY-5465
Status: Tony investigated it - not bug difference?
• Windows_x86_64:
1 additional failure in pack200 (not regression)
2) Dacapo: crash on Linux x86_32 & Linuxs_x86_64 (seems it is not intermittent)
3) DRLVM regression tests:
• Windows_x86: org.apache.harmony.drlvm.tests.regression.h5206
4) DRLVM tests:
• Windows_x86_64: classloader.StressLoader_jit crash (seems it is not
intermittent)
Status: according to Vladimir Beliaev this one is not critical and
should not block the release
5) EUTs:
• Windows x86: 3 failures
6) EGAx48:
• Windows_x86: failed
• Linux_x86: in progress (passed on the previous snapshot)
• Linux x86 64: failed
7) Eclipse TPTP:
• Linux_x86_64 - 5 failures: regression
Status: 5 failures (HARMONY-5347), won't be fixed in M5
+ agg_threadPowerWorkload_10_F (new one compared to the
previous snapshot)
8) Functional:
• On all platfroms:
api.java.security.F_KeyFactoryTest_01:
HARMONY-4857 - regression introduced in M3. Bug in third-party component
api.java.beans.beancontext.BeanContextTest
regression caused by changes in locale data
api.java.util.jar.Manifest
regression introduced by the fix of HARMONY-5473
api.java.text.MessageFormat
regression caused by migration to ICU HARMONY-5430
• Windows_x86: +1 failures
jit.HLO.devirt.Runtime.RuntimeExtend1 - not regression
• Linux_x86: +4 failures
functional.org.apache.harmony.test.func.jit.HLO.dce.deadstring
(intermittent?)
vm.cli.verbose - regression
vm.cli.verbose.verbose01 - regression
vm.cli.Xverbose.Xverbose07 - regression
• Windows_x86_64: +8 failures
jit.HLO.devirt.Runtime.RuntimeExtend1
not regression
jit.HLO.inline.ControlFlow.IfElse.IfElse1
regression since M3,looked intermittent in M4 but it stably fails
jit.HLO.peel.Switch -intemittent(?)
jpda.jdwp.scenario.EB01 - regression
jpda.jdwp.scenario.ST07 - regression
reg.vm.btest5717
regression since M3, looked intermittent in M4 but it stably fails
reg.vm.btest6353
failed on M3 too, (Andrey said might be issue with the test)
reg.vm.btest7214
regression since M3, looked intermittent in M4 but it stably fails
• Linux_x86_64: +12 failures
intermittent(?)
api.java.io.ObjectOutputStream.writeObjectReadObject0010
api.java.io.ObjectOutputStream.writeObjectReadObject0029
api.java.io.PushBackInputStream
api.java.lang.ref.F_PhantomReferenceTest_03
api.java.lang.ref.F_SoftReferenceTest_03
api.java.util.logging.Handler
vm.cli.verbose.verbose
regression:
jpda.jdwp.scenario.EB01
jpda.jdwp.scenario.ST07
reg.jit.btest4318
vm.cli.verbose.verbose01
reg.vm.btest6353
failed on M3 too, (Andrey said might be issue with the test?)
9) Geronimo Unit Tests
• Windows_x86_64: 4 failures
org.apache.geronimo.cxf - intermittent(?)
• Linux_x86_64: 2 failures
org.apache.geronimo.cxf - intermittent(?)
10) Reliability:
• Windows_x86:2 failures
api.net.DatagramTest - HARMONY-5531
api.serialization.SerializableClassesTest- HARMONY-5532
• Linux_x86: 3 failures
api.net.DatagramTest - HARMONY-5531
api.serialization.SerializableClassesTest- HARMONY-5532
api.text.DecimalFormat_Locales - intermittent(?)
• Linux x86 64 bit:
vm.classloading.ClassCastTest - failed on M4 too
api.kernel.thread.ThreadLocalTest - regression
11) Stress: need investigation
• Windows_x86: 1 failure
gc.frag.FragmentationFinalizer - intermittent(?)
• Linux_x86: 3 failure (failed on M4 too) HARMONY-5159
gc.frag.Fragmentation
gc.frag.FragmentationFinalizer
gc.frag.FragmentationReference
• Windows_x86_64: 4 failures
classloader.NotSynchThreads.SupIntf - regression
gc.frag.FragmentationFinalizer: HARMONY-5159
jpda.jdwp.scenario.MEMORY001 - failed on M4 too
jpda.jdwp.scenario.MEMORY003 - failed on M4 too
• Linux_x86_64: 2 failures
jpda.jdwp.scenario.MEMORY001 - failed on M4 too
jpda.jdwp.scenario.MEMORY003 - failed on M4 too
12) Struts: HARMONY-5498 is closed but the scenario still fails
13) VTS VM:
• Windows_x86_64 & Linux_x86_64
vm.jvmti.events.CompiledMethodLoad.CompiledMethodLoad0101
HARMONY-5347(regression) won't be fixed in M5
Thanks,
Stepan.
Re: [testing] second M5 candidate (r629320) testing status.
Posted by Eugene Ostrovsky <eu...@gmail.com>.
> 7) Eclipse TPTP:
> • Linux_x86_64 - 5 failures: regression
>
> Status: 5 failures (HARMONY-5347), won't be fixed in M5
> + agg_threadPowerWorkload_10_F (new one compared to the
> previous snapshot)
agg_threadPowerWorkload_10_F is one of the expected intermittently
failing tests. I've rechecked it by manual test run (it passed).
Not a regression.
Thanks, Eugene.
Re: [testing] second M5 candidate (r629320) testing status.
Posted by Tony Wu <wu...@gmail.com>.
On 2/22/08, Stepan Mishura <st...@gmail.com> wrote:
> Hi all,
>
> Here is r629320 snapshot testing status. Briefly, there are several
> failures: some of them are intermittent and/or known issues (i.e there
> is JIRA for tracking). Also there are several new regressions for
> investigation if they are blockers for M5 or not. I think that the
> most serious one is a crash of Dacapo on Linux'es. Could anyone to
> look into?
>
> Please add your comments and clarifications.
>
> 1) Classlib:
>
> 5 failures in text module because of HARMONY-5465
>
> Status: Tony investigated it - not bug difference?
I believe it is a non-bug difference but have not got an agreement
with others. Anyway it is not a big deal, we have difference in
Collation aganist RI (and M4) only in the sepcial
Locale("es","","TRADITIONAL"). I suggest to move it out of M5 and fix
it later when we got an agreement. HARMONY-5542 is raised to record
this problem.
>
> • Windows_x86_64:
> 1 additional failure in pack200 (not regression)
>
> 2) Dacapo: crash on Linux x86_32 & Linuxs_x86_64 (seems it is not intermittent)
>
> 3) DRLVM regression tests:
> • Windows_x86: org.apache.harmony.drlvm.tests.regression.h5206
>
> 4) DRLVM tests:
> • Windows_x86_64: classloader.StressLoader_jit crash (seems it is not
> intermittent)
>
> Status: according to Vladimir Beliaev this one is not critical and
> should not block the release
>
> 5) EUTs:
> • Windows x86: 3 failures
>
> 6) EGAx48:
> • Windows_x86: failed
> • Linux_x86: in progress (passed on the previous snapshot)
> • Linux x86 64: failed
>
> 7) Eclipse TPTP:
> • Linux_x86_64 - 5 failures: regression
>
> Status: 5 failures (HARMONY-5347), won't be fixed in M5
> + agg_threadPowerWorkload_10_F (new one compared to the
> previous snapshot)
>
> 8) Functional:
> • On all platfroms:
> api.java.security.F_KeyFactoryTest_01:
> HARMONY-4857 - regression introduced in M3. Bug in third-party component
> api.java.beans.beancontext.BeanContextTest
> regression caused by changes in locale data
> api.java.util.jar.Manifest
> regression introduced by the fix of HARMONY-5473
> api.java.text.MessageFormat
> regression caused by migration to ICU HARMONY-5430
>
>
> • Windows_x86: +1 failures
> jit.HLO.devirt.Runtime.RuntimeExtend1 - not regression
>
> • Linux_x86: +4 failures
> functional.org.apache.harmony.test.func.jit.HLO.dce.deadstring
> (intermittent?)
> vm.cli.verbose - regression
> vm.cli.verbose.verbose01 - regression
> vm.cli.Xverbose.Xverbose07 - regression
>
> • Windows_x86_64: +8 failures
> jit.HLO.devirt.Runtime.RuntimeExtend1
> not regression
> jit.HLO.inline.ControlFlow.IfElse.IfElse1
> regression since M3,looked intermittent in M4 but it stably fails
> jit.HLO.peel.Switch -intemittent(?)
> jpda.jdwp.scenario.EB01 - regression
> jpda.jdwp.scenario.ST07 - regression
> reg.vm.btest5717
> regression since M3, looked intermittent in M4 but it stably fails
> reg.vm.btest6353
> failed on M3 too, (Andrey said might be issue with the test)
> reg.vm.btest7214
> regression since M3, looked intermittent in M4 but it stably fails
>
> • Linux_x86_64: +12 failures
> intermittent(?)
> api.java.io.ObjectOutputStream.writeObjectReadObject0010
> api.java.io.ObjectOutputStream.writeObjectReadObject0029
> api.java.io.PushBackInputStream
> api.java.lang.ref.F_PhantomReferenceTest_03
> api.java.lang.ref.F_SoftReferenceTest_03
> api.java.util.logging.Handler
> vm.cli.verbose.verbose
>
> regression:
> jpda.jdwp.scenario.EB01
> jpda.jdwp.scenario.ST07
> reg.jit.btest4318
> vm.cli.verbose.verbose01
>
> reg.vm.btest6353
> failed on M3 too, (Andrey said might be issue with the test?)
>
> 9) Geronimo Unit Tests
>
> • Windows_x86_64: 4 failures
> org.apache.geronimo.cxf - intermittent(?)
>
> • Linux_x86_64: 2 failures
> org.apache.geronimo.cxf - intermittent(?)
>
> 10) Reliability:
>
> • Windows_x86:2 failures
> api.net.DatagramTest - HARMONY-5531
> api.serialization.SerializableClassesTest- HARMONY-5532
>
> • Linux_x86: 3 failures
> api.net.DatagramTest - HARMONY-5531
> api.serialization.SerializableClassesTest- HARMONY-5532
> api.text.DecimalFormat_Locales - intermittent(?)
>
> • Linux x86 64 bit:
> vm.classloading.ClassCastTest - failed on M4 too
> api.kernel.thread.ThreadLocalTest - regression
>
> 11) Stress: need investigation
> • Windows_x86: 1 failure
> gc.frag.FragmentationFinalizer - intermittent(?)
>
> • Linux_x86: 3 failure (failed on M4 too) HARMONY-5159
> gc.frag.Fragmentation
> gc.frag.FragmentationFinalizer
> gc.frag.FragmentationReference
>
> • Windows_x86_64: 4 failures
> classloader.NotSynchThreads.SupIntf - regression
> gc.frag.FragmentationFinalizer: HARMONY-5159
> jpda.jdwp.scenario.MEMORY001 - failed on M4 too
> jpda.jdwp.scenario.MEMORY003 - failed on M4 too
>
> • Linux_x86_64: 2 failures
> jpda.jdwp.scenario.MEMORY001 - failed on M4 too
> jpda.jdwp.scenario.MEMORY003 - failed on M4 too
>
> 12) Struts: HARMONY-5498 is closed but the scenario still fails
>
> 13) VTS VM:
> • Windows_x86_64 & Linux_x86_64
> vm.jvmti.events.CompiledMethodLoad.CompiledMethodLoad0101
> HARMONY-5347(regression) won't be fixed in M5
>
> Thanks,
> Stepan.
>
--
Tony Wu
China Software Development Lab, IBM
Re: [testing] second M5 candidate (r629320) testing status.
Posted by Stepan Mishura <st...@gmail.com>.
On 2/22/08, Stepan Mishura <st...@gmail.com> wrote:
> Hi all,
>
> Here is r629320 snapshot testing status. Briefly, there are several
> failures: some of them are intermittent and/or known issues (i.e there
> is JIRA for tracking). Also there are several new regressions for
> investigation if they are blockers for M5 or not. I think that the
> most serious one is a crash of Dacapo on Linux'es. Could anyone to
> look into?
>
> Please add your comments and clarifications.
>
> 1) Classlib:
>
> 5 failures in text module because of HARMONY-5465
>
> Status: Tony investigated it - not bug difference?
>
> • Windows_x86_64:
> 1 additional failure in pack200 (not regression)
>
> 2) Dacapo: crash on Linux x86_32 & Linuxs_x86_64 (seems it is not intermittent)
>
Well, the issue is intermittently reproducible on the CC host but I
can not reproduce it on another host. Can anyone try to reproduce it?
If not I think it is not a blocker for M5. Objections?
Thanks,
Stepan.
> 3) DRLVM regression tests:
> • Windows_x86: org.apache.harmony.drlvm.tests.regression.h5206
>
> 4) DRLVM tests:
> • Windows_x86_64: classloader.StressLoader_jit crash (seems it is not
> intermittent)
>
> Status: according to Vladimir Beliaev this one is not critical and
> should not block the release
>
> 5) EUTs:
> • Windows x86: 3 failures
>
> 6) EGAx48:
> • Windows_x86: failed
> • Linux_x86: in progress (passed on the previous snapshot)
> • Linux x86 64: failed
>
> 7) Eclipse TPTP:
> • Linux_x86_64 - 5 failures: regression
>
> Status: 5 failures (HARMONY-5347), won't be fixed in M5
> + agg_threadPowerWorkload_10_F (new one compared to the
> previous snapshot)
>
> 8) Functional:
> • On all platfroms:
> api.java.security.F_KeyFactoryTest_01:
> HARMONY-4857 - regression introduced in M3. Bug in third-party component
> api.java.beans.beancontext.BeanContextTest
> regression caused by changes in locale data
> api.java.util.jar.Manifest
> regression introduced by the fix of HARMONY-5473
> api.java.text.MessageFormat
> regression caused by migration to ICU HARMONY-5430
>
>
> • Windows_x86: +1 failures
> jit.HLO.devirt.Runtime.RuntimeExtend1 - not regression
>
> • Linux_x86: +4 failures
> functional.org.apache.harmony.test.func.jit.HLO.dce.deadstring
> (intermittent?)
> vm.cli.verbose - regression
> vm.cli.verbose.verbose01 - regression
> vm.cli.Xverbose.Xverbose07 - regression
>
> • Windows_x86_64: +8 failures
> jit.HLO.devirt.Runtime.RuntimeExtend1
> not regression
> jit.HLO.inline.ControlFlow.IfElse.IfElse1
> regression since M3,looked intermittent in M4 but it stably fails
> jit.HLO.peel.Switch -intemittent(?)
> jpda.jdwp.scenario.EB01 - regression
> jpda.jdwp.scenario.ST07 - regression
> reg.vm.btest5717
> regression since M3, looked intermittent in M4 but it stably fails
> reg.vm.btest6353
> failed on M3 too, (Andrey said might be issue with the test)
> reg.vm.btest7214
> regression since M3, looked intermittent in M4 but it stably fails
>
> • Linux_x86_64: +12 failures
> intermittent(?)
> api.java.io.ObjectOutputStream.writeObjectReadObject0010
> api.java.io.ObjectOutputStream.writeObjectReadObject0029
> api.java.io.PushBackInputStream
> api.java.lang.ref.F_PhantomReferenceTest_03
> api.java.lang.ref.F_SoftReferenceTest_03
> api.java.util.logging.Handler
> vm.cli.verbose.verbose
>
> regression:
> jpda.jdwp.scenario.EB01
> jpda.jdwp.scenario.ST07
> reg.jit.btest4318
> vm.cli.verbose.verbose01
>
> reg.vm.btest6353
> failed on M3 too, (Andrey said might be issue with the test?)
>
> 9) Geronimo Unit Tests
>
> • Windows_x86_64: 4 failures
> org.apache.geronimo.cxf - intermittent(?)
>
> • Linux_x86_64: 2 failures
> org.apache.geronimo.cxf - intermittent(?)
>
> 10) Reliability:
>
> • Windows_x86:2 failures
> api.net.DatagramTest - HARMONY-5531
> api.serialization.SerializableClassesTest- HARMONY-5532
>
> • Linux_x86: 3 failures
> api.net.DatagramTest - HARMONY-5531
> api.serialization.SerializableClassesTest- HARMONY-5532
> api.text.DecimalFormat_Locales - intermittent(?)
>
> • Linux x86 64 bit:
> vm.classloading.ClassCastTest - failed on M4 too
> api.kernel.thread.ThreadLocalTest - regression
>
> 11) Stress: need investigation
> • Windows_x86: 1 failure
> gc.frag.FragmentationFinalizer - intermittent(?)
>
> • Linux_x86: 3 failure (failed on M4 too) HARMONY-5159
> gc.frag.Fragmentation
> gc.frag.FragmentationFinalizer
> gc.frag.FragmentationReference
>
> • Windows_x86_64: 4 failures
> classloader.NotSynchThreads.SupIntf - regression
> gc.frag.FragmentationFinalizer: HARMONY-5159
> jpda.jdwp.scenario.MEMORY001 - failed on M4 too
> jpda.jdwp.scenario.MEMORY003 - failed on M4 too
>
> • Linux_x86_64: 2 failures
> jpda.jdwp.scenario.MEMORY001 - failed on M4 too
> jpda.jdwp.scenario.MEMORY003 - failed on M4 too
>
> 12) Struts: HARMONY-5498 is closed but the scenario still fails
>
> 13) VTS VM:
> • Windows_x86_64 & Linux_x86_64
> vm.jvmti.events.CompiledMethodLoad.CompiledMethodLoad0101
> HARMONY-5347(regression) won't be fixed in M5
>
> Thanks,
> Stepan.
>
Re: [testing] second M5 candidate (r629320) testing status.
Posted by Alexey Petrenko <al...@gmail.com>.
2008/2/22, Stepan Mishura <st...@gmail.com>:
> 8) Functional:
> • On all platfroms:
> api.java.security.F_KeyFactoryTest_01:
> HARMONY-4857 - regression introduced in M3. Bug in third-party component
> api.java.beans.beancontext.BeanContextTest
> regression caused by changes in locale data
> api.java.util.jar.Manifest
> regression introduced by the fix of HARMONY-5473
It was decided to keep this patch. See "[APPROVAL] revert r620461" thread.
SY, Alexey
Re: [testing] second M5 candidate (r629320) testing status.
Posted by Stepan Mishura <st...@gmail.com>.
On 2/26/08, Tim Ellison <t....@gmail.com> wrote:
> Stepan Mishura wrote:
> > So it looks like that there are no critical issues for r629320.
> > Should we start voting to declare r629320 as M5?
>
>
> Wonderful -- looks like I came back at just the right time (to avoid
> testing work <g>)
>
> Starting a vote is fine by me. We should be voting on the source bundle
> as our official M5 artifact, the binaries are a convenience. We need a
> minimum of 3 +1's from the PMC for it to pass.
>
> Do you want me to conduct the vote?
OK. I'll start a separate thread.
-Stepan.
>
> Regards,
> Tim
>
Re: [testing] second M5 candidate (r629320) testing status.
Posted by Tim Ellison <t....@gmail.com>.
Stepan Mishura wrote:
> So it looks like that there are no critical issues for r629320.
> Should we start voting to declare r629320 as M5?
Wonderful -- looks like I came back at just the right time (to avoid
testing work <g>)
Starting a vote is fine by me. We should be voting on the source bundle
as our official M5 artifact, the binaries are a convenience. We need a
minimum of 3 +1's from the PMC for it to pass.
Do you want me to conduct the vote?
Regards,
Tim
Re: [testing] second M5 candidate (r629320) testing status.
Posted by Stepan Mishura <st...@gmail.com>.
On 2/26/08, Tim Ellison <t....@gmail.com> wrote:
<SNIP>> >>
> >> 6) EGAx48:
> >> • Windows_x86: failed - HARMONY-5545, (configuration issue, scenario
> >> can't start Eclipse)
> >
> > I've restarted the scenario and Eclipse started successfully.
> > Let's see if the restarted run is successful or not .
>
> Just catching-up on mail. So you are going to run a new 48 hr test?
>
Yes, I restarted the scenario but I think it shouldn't block M5
milestone release.
So it looks like that there are no critical issues for r629320.
Should we start voting to declare r629320 as M5?
Thanks,
Stepan.
> Regards,
> Tim
>
> >> • Linux_x86: passed
> >> • Linux x86 64: failed - HARMONY-5546, (test issue, scenario can't
> >> recognize FireFox Help window due to browser window has no name
> >> identifier)
> >>
> >> Thanks,
> >> Ilya
> >>
> >
>
Re: [testing] second M5 candidate (r629320) testing status.
Posted by Tim Ellison <t....@gmail.com>.
Stepan Mishura wrote:
> On 2/25/08, Ilya Leviev <il...@gmail.com> wrote:
>> Hi,
>>
>> On 2/22/08, Stepan Mishura <st...@gmail.com> wrote:
>>> Hi all,
>>>
>>> Here is r629320 snapshot testing status. Briefly, there are several
>>> failures: some of them are intermittent and/or known issues (i.e there
>>> is JIRA for tracking). Also there are several new regressions for
>>> investigation if they are blockers for M5 or not. I think that the
>>> most serious one is a crash of Dacapo on Linux'es. Could anyone to
>>> look into?
>>>
>>> Please add your comments and clarifications.
>>
>> 11) Stress:
>> • Windows_x86: 1 failure
>> gc.frag.FragmentationFinalizer.FragmentationFinalizerWaitTest -
>> HARMONY-5341 -intermittent
>>
>> • Linux_x86: 3 failure (failed on M4 too) HARMONY-5159 - enabling of tests
>> gc.frag.Fragmentation
>> gc.frag.FragmentationFinalizer
>> gc.frag.FragmentationReference
>>
>> • Linux_x86_64: 2 failures
>> jpda.jdwp.scenario.MEMORY001 - failed on M4 too - HARMONY-5047 patch
>> fix prepared
>> jpda.jdwp.scenario.MEMORY003 - failed on M4 too - HARMONY-5047 patch
>> fix prepared
>>
>>
>> 6) EGAx48:
>> • Windows_x86: failed - HARMONY-5545, (configuration issue, scenario
>> can't start Eclipse)
>
> I've restarted the scenario and Eclipse started successfully.
> Let's see if the restarted run is successful or not .
Just catching-up on mail. So you are going to run a new 48 hr test?
Regards,
Tim
>> • Linux_x86: passed
>> • Linux x86 64: failed - HARMONY-5546, (test issue, scenario can't
>> recognize FireFox Help window due to browser window has no name
>> identifier)
>>
>> Thanks,
>> Ilya
>>
>
Re: [testing] second M5 candidate (r629320) testing status.
Posted by Stepan Mishura <st...@gmail.com>.
On 2/25/08, Ilya Leviev <il...@gmail.com> wrote:
> Hi,
>
> On 2/22/08, Stepan Mishura <st...@gmail.com> wrote:
> > Hi all,
> >
> > Here is r629320 snapshot testing status. Briefly, there are several
> > failures: some of them are intermittent and/or known issues (i.e there
> > is JIRA for tracking). Also there are several new regressions for
> > investigation if they are blockers for M5 or not. I think that the
> > most serious one is a crash of Dacapo on Linux'es. Could anyone to
> > look into?
> >
> > Please add your comments and clarifications.
>
>
> 11) Stress:
> • Windows_x86: 1 failure
> gc.frag.FragmentationFinalizer.FragmentationFinalizerWaitTest -
> HARMONY-5341 -intermittent
>
> • Linux_x86: 3 failure (failed on M4 too) HARMONY-5159 - enabling of tests
> gc.frag.Fragmentation
> gc.frag.FragmentationFinalizer
> gc.frag.FragmentationReference
>
> • Linux_x86_64: 2 failures
> jpda.jdwp.scenario.MEMORY001 - failed on M4 too - HARMONY-5047 patch
> fix prepared
> jpda.jdwp.scenario.MEMORY003 - failed on M4 too - HARMONY-5047 patch
> fix prepared
>
>
> 6) EGAx48:
> • Windows_x86: failed - HARMONY-5545, (configuration issue, scenario
> can't start Eclipse)
I've restarted the scenario and Eclipse started successfully.
Let's see if the restarted run is successful or not .
-Stepan.
> • Linux_x86: passed
> • Linux x86 64: failed - HARMONY-5546, (test issue, scenario can't
> recognize FireFox Help window due to browser window has no name
> identifier)
>
> Thanks,
> Ilya
>
Re: [testing] second M5 candidate (r629320) testing status.
Posted by Ilya Leviev <il...@gmail.com>.
Hi,
On 2/22/08, Stepan Mishura <st...@gmail.com> wrote:
> Hi all,
>
> Here is r629320 snapshot testing status. Briefly, there are several
> failures: some of them are intermittent and/or known issues (i.e there
> is JIRA for tracking). Also there are several new regressions for
> investigation if they are blockers for M5 or not. I think that the
> most serious one is a crash of Dacapo on Linux'es. Could anyone to
> look into?
>
> Please add your comments and clarifications.
11) Stress:
• Windows_x86: 1 failure
gc.frag.FragmentationFinalizer.FragmentationFinalizerWaitTest -
HARMONY-5341 -intermittent
• Linux_x86: 3 failure (failed on M4 too) HARMONY-5159 - enabling of tests
gc.frag.Fragmentation
gc.frag.FragmentationFinalizer
gc.frag.FragmentationReference
• Linux_x86_64: 2 failures
jpda.jdwp.scenario.MEMORY001 - failed on M4 too - HARMONY-5047 patch
fix prepared
jpda.jdwp.scenario.MEMORY003 - failed on M4 too - HARMONY-5047 patch
fix prepared
6) EGAx48:
• Windows_x86: failed - HARMONY-5545, (configuration issue, scenario
can't start Eclipse)
• Linux_x86: passed
• Linux x86 64: failed - HARMONY-5546, (test issue, scenario can't
recognize FireFox Help window due to browser window has no name
identifier)
Thanks,
Ilya
Re: [testing] second M5 candidate (r629320) testing status.
Posted by Stepan Mishura <st...@gmail.com>.
On 2/22/08, Alexei Zakharov <al...@gmail.com> wrote:
> Stepan,
>
> > 12) Struts: HARMONY-5498 is closed but the scenario still fails
>
> The error report looks like Struts resource files weren't properly
> updated. Could you ensure all files in build/checkouts/struts_test are
> up-to-date and there was no local modifications made?
Thanks Alexei!
I missed that scenario's resource files were updated, sorry for the confusion.
-Stepan.
>
> Thanks,
> Alexei
>
>
> 2008/2/22, Stepan Mishura <st...@gmail.com>:
> > Hi all,
> >
> > Here is r629320 snapshot testing status. Briefly, there are several
> > failures: some of them are intermittent and/or known issues (i.e there
> > is JIRA for tracking). Also there are several new regressions for
> > investigation if they are blockers for M5 or not. I think that the
> > most serious one is a crash of Dacapo on Linux'es. Could anyone to
> > look into?
> >
> > Please add your comments and clarifications.
> >
> > 1) Classlib:
> >
> > 5 failures in text module because of HARMONY-5465
> >
> > Status: Tony investigated it - not bug difference?
> >
> > • Windows_x86_64:
> > 1 additional failure in pack200 (not regression)
> >
> > 2) Dacapo: crash on Linux x86_32 & Linuxs_x86_64 (seems it is not intermittent)
> >
> > 3) DRLVM regression tests:
> > • Windows_x86: org.apache.harmony.drlvm.tests.regression.h5206
> >
> > 4) DRLVM tests:
> > • Windows_x86_64: classloader.StressLoader_jit crash (seems it is not
> > intermittent)
> >
> > Status: according to Vladimir Beliaev this one is not critical and
> > should not block the release
> >
> > 5) EUTs:
> > • Windows x86: 3 failures
> >
> > 6) EGAx48:
> > • Windows_x86: failed
> > • Linux_x86: in progress (passed on the previous snapshot)
> > • Linux x86 64: failed
> >
> > 7) Eclipse TPTP:
> > • Linux_x86_64 - 5 failures: regression
> >
> > Status: 5 failures (HARMONY-5347), won't be fixed in M5
> > + agg_threadPowerWorkload_10_F (new one compared to the
> > previous snapshot)
> >
> > 8) Functional:
> > • On all platfroms:
> > api.java.security.F_KeyFactoryTest_01:
> > HARMONY-4857 - regression introduced in M3. Bug in third-party component
> > api.java.beans.beancontext.BeanContextTest
> > regression caused by changes in locale data
> > api.java.util.jar.Manifest
> > regression introduced by the fix of HARMONY-5473
> > api.java.text.MessageFormat
> > regression caused by migration to ICU HARMONY-5430
> >
> >
> > • Windows_x86: +1 failures
> > jit.HLO.devirt.Runtime.RuntimeExtend1 - not regression
> >
> > • Linux_x86: +4 failures
> > functional.org.apache.harmony.test.func.jit.HLO.dce.deadstring
> > (intermittent?)
> > vm.cli.verbose - regression
> > vm.cli.verbose.verbose01 - regression
> > vm.cli.Xverbose.Xverbose07 - regression
> >
> > • Windows_x86_64: +8 failures
> > jit.HLO.devirt.Runtime.RuntimeExtend1
> > not regression
> > jit.HLO.inline.ControlFlow.IfElse.IfElse1
> > regression since M3,looked intermittent in M4 but it stably fails
> > jit.HLO.peel.Switch -intemittent(?)
> > jpda.jdwp.scenario.EB01 - regression
> > jpda.jdwp.scenario.ST07 - regression
> > reg.vm.btest5717
> > regression since M3, looked intermittent in M4 but it stably fails
> > reg.vm.btest6353
> > failed on M3 too, (Andrey said might be issue with the test)
> > reg.vm.btest7214
> > regression since M3, looked intermittent in M4 but it stably fails
> >
> > • Linux_x86_64: +12 failures
> > intermittent(?)
> > api.java.io.ObjectOutputStream.writeObjectReadObject0010
> > api.java.io.ObjectOutputStream.writeObjectReadObject0029
> > api.java.io.PushBackInputStream
> > api.java.lang.ref.F_PhantomReferenceTest_03
> > api.java.lang.ref.F_SoftReferenceTest_03
> > api.java.util.logging.Handler
> > vm.cli.verbose.verbose
> >
> > regression:
> > jpda.jdwp.scenario.EB01
> > jpda.jdwp.scenario.ST07
> > reg.jit.btest4318
> > vm.cli.verbose.verbose01
> >
> > reg.vm.btest6353
> > failed on M3 too, (Andrey said might be issue with the test?)
> >
> > 9) Geronimo Unit Tests
> >
> > • Windows_x86_64: 4 failures
> > org.apache.geronimo.cxf - intermittent(?)
> >
> > • Linux_x86_64: 2 failures
> > org.apache.geronimo.cxf - intermittent(?)
> >
> > 10) Reliability:
> >
> > • Windows_x86:2 failures
> > api.net.DatagramTest - HARMONY-5531
> > api.serialization.SerializableClassesTest- HARMONY-5532
> >
> > • Linux_x86: 3 failures
> > api.net.DatagramTest - HARMONY-5531
> > api.serialization.SerializableClassesTest- HARMONY-5532
> > api.text.DecimalFormat_Locales - intermittent(?)
> >
> > • Linux x86 64 bit:
> > vm.classloading.ClassCastTest - failed on M4 too
> > api.kernel.thread.ThreadLocalTest - regression
> >
> > 11) Stress: need investigation
> > • Windows_x86: 1 failure
> > gc.frag.FragmentationFinalizer - intermittent(?)
> >
> > • Linux_x86: 3 failure (failed on M4 too) HARMONY-5159
> > gc.frag.Fragmentation
> > gc.frag.FragmentationFinalizer
> > gc.frag.FragmentationReference
> >
> > • Windows_x86_64: 4 failures
> > classloader.NotSynchThreads.SupIntf - regression
> > gc.frag.FragmentationFinalizer: HARMONY-5159
> > jpda.jdwp.scenario.MEMORY001 - failed on M4 too
> > jpda.jdwp.scenario.MEMORY003 - failed on M4 too
> >
> > • Linux_x86_64: 2 failures
> > jpda.jdwp.scenario.MEMORY001 - failed on M4 too
> > jpda.jdwp.scenario.MEMORY003 - failed on M4 too
> >
> > 12) Struts: HARMONY-5498 is closed but the scenario still fails
> >
> > 13) VTS VM:
> > • Windows_x86_64 & Linux_x86_64
> > vm.jvmti.events.CompiledMethodLoad.CompiledMethodLoad0101
> > HARMONY-5347(regression) won't be fixed in M5
> >
> > Thanks,
> >
> > Stepan.
> >
>
Re: [testing] second M5 candidate (r629320) testing status.
Posted by Alexei Zakharov <al...@gmail.com>.
Stepan,
> 12) Struts: HARMONY-5498 is closed but the scenario still fails
The error report looks like Struts resource files weren't properly
updated. Could you ensure all files in build/checkouts/struts_test are
up-to-date and there was no local modifications made?
Thanks,
Alexei
2008/2/22, Stepan Mishura <st...@gmail.com>:
> Hi all,
>
> Here is r629320 snapshot testing status. Briefly, there are several
> failures: some of them are intermittent and/or known issues (i.e there
> is JIRA for tracking). Also there are several new regressions for
> investigation if they are blockers for M5 or not. I think that the
> most serious one is a crash of Dacapo on Linux'es. Could anyone to
> look into?
>
> Please add your comments and clarifications.
>
> 1) Classlib:
>
> 5 failures in text module because of HARMONY-5465
>
> Status: Tony investigated it - not bug difference?
>
> • Windows_x86_64:
> 1 additional failure in pack200 (not regression)
>
> 2) Dacapo: crash on Linux x86_32 & Linuxs_x86_64 (seems it is not intermittent)
>
> 3) DRLVM regression tests:
> • Windows_x86: org.apache.harmony.drlvm.tests.regression.h5206
>
> 4) DRLVM tests:
> • Windows_x86_64: classloader.StressLoader_jit crash (seems it is not
> intermittent)
>
> Status: according to Vladimir Beliaev this one is not critical and
> should not block the release
>
> 5) EUTs:
> • Windows x86: 3 failures
>
> 6) EGAx48:
> • Windows_x86: failed
> • Linux_x86: in progress (passed on the previous snapshot)
> • Linux x86 64: failed
>
> 7) Eclipse TPTP:
> • Linux_x86_64 - 5 failures: regression
>
> Status: 5 failures (HARMONY-5347), won't be fixed in M5
> + agg_threadPowerWorkload_10_F (new one compared to the
> previous snapshot)
>
> 8) Functional:
> • On all platfroms:
> api.java.security.F_KeyFactoryTest_01:
> HARMONY-4857 - regression introduced in M3. Bug in third-party component
> api.java.beans.beancontext.BeanContextTest
> regression caused by changes in locale data
> api.java.util.jar.Manifest
> regression introduced by the fix of HARMONY-5473
> api.java.text.MessageFormat
> regression caused by migration to ICU HARMONY-5430
>
>
> • Windows_x86: +1 failures
> jit.HLO.devirt.Runtime.RuntimeExtend1 - not regression
>
> • Linux_x86: +4 failures
> functional.org.apache.harmony.test.func.jit.HLO.dce.deadstring
> (intermittent?)
> vm.cli.verbose - regression
> vm.cli.verbose.verbose01 - regression
> vm.cli.Xverbose.Xverbose07 - regression
>
> • Windows_x86_64: +8 failures
> jit.HLO.devirt.Runtime.RuntimeExtend1
> not regression
> jit.HLO.inline.ControlFlow.IfElse.IfElse1
> regression since M3,looked intermittent in M4 but it stably fails
> jit.HLO.peel.Switch -intemittent(?)
> jpda.jdwp.scenario.EB01 - regression
> jpda.jdwp.scenario.ST07 - regression
> reg.vm.btest5717
> regression since M3, looked intermittent in M4 but it stably fails
> reg.vm.btest6353
> failed on M3 too, (Andrey said might be issue with the test)
> reg.vm.btest7214
> regression since M3, looked intermittent in M4 but it stably fails
>
> • Linux_x86_64: +12 failures
> intermittent(?)
> api.java.io.ObjectOutputStream.writeObjectReadObject0010
> api.java.io.ObjectOutputStream.writeObjectReadObject0029
> api.java.io.PushBackInputStream
> api.java.lang.ref.F_PhantomReferenceTest_03
> api.java.lang.ref.F_SoftReferenceTest_03
> api.java.util.logging.Handler
> vm.cli.verbose.verbose
>
> regression:
> jpda.jdwp.scenario.EB01
> jpda.jdwp.scenario.ST07
> reg.jit.btest4318
> vm.cli.verbose.verbose01
>
> reg.vm.btest6353
> failed on M3 too, (Andrey said might be issue with the test?)
>
> 9) Geronimo Unit Tests
>
> • Windows_x86_64: 4 failures
> org.apache.geronimo.cxf - intermittent(?)
>
> • Linux_x86_64: 2 failures
> org.apache.geronimo.cxf - intermittent(?)
>
> 10) Reliability:
>
> • Windows_x86:2 failures
> api.net.DatagramTest - HARMONY-5531
> api.serialization.SerializableClassesTest- HARMONY-5532
>
> • Linux_x86: 3 failures
> api.net.DatagramTest - HARMONY-5531
> api.serialization.SerializableClassesTest- HARMONY-5532
> api.text.DecimalFormat_Locales - intermittent(?)
>
> • Linux x86 64 bit:
> vm.classloading.ClassCastTest - failed on M4 too
> api.kernel.thread.ThreadLocalTest - regression
>
> 11) Stress: need investigation
> • Windows_x86: 1 failure
> gc.frag.FragmentationFinalizer - intermittent(?)
>
> • Linux_x86: 3 failure (failed on M4 too) HARMONY-5159
> gc.frag.Fragmentation
> gc.frag.FragmentationFinalizer
> gc.frag.FragmentationReference
>
> • Windows_x86_64: 4 failures
> classloader.NotSynchThreads.SupIntf - regression
> gc.frag.FragmentationFinalizer: HARMONY-5159
> jpda.jdwp.scenario.MEMORY001 - failed on M4 too
> jpda.jdwp.scenario.MEMORY003 - failed on M4 too
>
> • Linux_x86_64: 2 failures
> jpda.jdwp.scenario.MEMORY001 - failed on M4 too
> jpda.jdwp.scenario.MEMORY003 - failed on M4 too
>
> 12) Struts: HARMONY-5498 is closed but the scenario still fails
>
> 13) VTS VM:
> • Windows_x86_64 & Linux_x86_64
> vm.jvmti.events.CompiledMethodLoad.CompiledMethodLoad0101
> HARMONY-5347(regression) won't be fixed in M5
>
> Thanks,
>
> Stepan.
>
Re: [testing] second M5 candidate (r629320) testing status.
Posted by Vladimir Beliaev <vl...@gmail.com>.
I've checked 3 failures of EUT on winx86 - not reproduced locally. So it is
nothing to work on => nothing to block the release.
And I'm really glad to see EUT on Linux green this time.
Thanks
Vladimir
2008/2/22, Gregory Shimansky <gs...@apache.org>:
>
> Stepan Mishura said the following on 22.02.2008 8:13:
> > Hi all,
> >
> > Here is r629320 snapshot testing status. Briefly, there are several
> > failures: some of them are intermittent and/or known issues (i.e there
> > is JIRA for tracking). Also there are several new regressions for
> > investigation if they are blockers for M5 or not. I think that the
> > most serious one is a crash of Dacapo on Linux'es. Could anyone to
> > look into?
> >
> > Please add your comments and clarifications.
> >
> > 1) Classlib:
> >
> > 5 failures in text module because of HARMONY-5465
> >
> > Status: Tony investigated it - not bug difference?
> >
> > • Windows_x86_64:
> > 1 additional failure in pack200 (not regression)
> >
> > 2) Dacapo: crash on Linux x86_32 & Linuxs_x86_64 (seems it is not
> intermittent)
> >
> > 3) DRLVM regression tests:
> > • Windows_x86: org.apache.harmony.drlvm.tests.regression.h5206
>
> This is a bug that was never actually fixed. Looking at it, it was
> discovered even in M3. It is an intermittent problem with volatile
> fields and it is not a regression.
>
> > 4) DRLVM tests:
> > • Windows_x86_64: classloader.StressLoader_jit crash (seems it is not
> > intermittent)
> >
> > Status: according to Vladimir Beliaev this one is not critical and
> > should not block the release
> >
> > 5) EUTs:
> > • Windows x86: 3 failures
> >
> > 6) EGAx48:
> > • Windows_x86: failed
> > • Linux_x86: in progress (passed on the previous snapshot)
> > • Linux x86 64: failed
> >
> > 7) Eclipse TPTP:
> > • Linux_x86_64 - 5 failures: regression
> >
> > Status: 5 failures (HARMONY-5347), won't be fixed in M5
> > + agg_threadPowerWorkload_10_F (new one compared to the
> > previous snapshot)
> >
> > 8) Functional:
> > • On all platfroms:
> > api.java.security.F_KeyFactoryTest_01:
> > HARMONY-4857 - regression introduced in M3. Bug in third-party
> component
> > api.java.beans.beancontext.BeanContextTest
> > regression caused by changes in locale data
> > api.java.util.jar.Manifest
> > regression introduced by the fix of HARMONY-5473
> > api.java.text.MessageFormat
> > regression caused by migration to ICU HARMONY-5430
> >
> >
> > • Windows_x86: +1 failures
> > jit.HLO.devirt.Runtime.RuntimeExtend1 - not regression
> >
> > • Linux_x86: +4 failures
> > functional.org.apache.harmony.test.func.jit.HLO.dce.deadstring
> > (intermittent?)
> > vm.cli.verbose - regression
> > vm.cli.verbose.verbose01 - regression
> > vm.cli.Xverbose.Xverbose07 - regression
> >
> > • Windows_x86_64: +8 failures
> > jit.HLO.devirt.Runtime.RuntimeExtend1
> > not regression
> > jit.HLO.inline.ControlFlow.IfElse.IfElse1
> > regression since M3,looked intermittent in M4 but it stably fails
> > jit.HLO.peel.Switch -intemittent(?)
> > jpda.jdwp.scenario.EB01 - regression
> > jpda.jdwp.scenario.ST07 - regression
> > reg.vm.btest5717
> > regression since M3, looked intermittent in M4 but it stably fails
> > reg.vm.btest6353
> > failed on M3 too, (Andrey said might be issue with the test)
> > reg.vm.btest7214
> > regression since M3, looked intermittent in M4 but it stably fails
> >
> > • Linux_x86_64: +12 failures
> > intermittent(?)
> > api.java.io.ObjectOutputStream.writeObjectReadObject0010
> > api.java.io.ObjectOutputStream.writeObjectReadObject0029
> > api.java.io.PushBackInputStream
> > api.java.lang.ref.F_PhantomReferenceTest_03
> > api.java.lang.ref.F_SoftReferenceTest_03
> > api.java.util.logging.Handler
> > vm.cli.verbose.verbose
> >
> > regression:
> > jpda.jdwp.scenario.EB01
> > jpda.jdwp.scenario.ST07
> > reg.jit.btest4318
> > vm.cli.verbose.verbose01
> >
> > reg.vm.btest6353
> > failed on M3 too, (Andrey said might be issue with the test?)
> >
> > 9) Geronimo Unit Tests
> >
> > • Windows_x86_64: 4 failures
> > org.apache.geronimo.cxf - intermittent(?)
> >
> > • Linux_x86_64: 2 failures
> > org.apache.geronimo.cxf - intermittent(?)
> >
> > 10) Reliability:
> >
> > • Windows_x86:2 failures
> > api.net.DatagramTest - HARMONY-5531
> > api.serialization.SerializableClassesTest- HARMONY-5532
> >
> > • Linux_x86: 3 failures
> > api.net.DatagramTest - HARMONY-5531
> > api.serialization.SerializableClassesTest- HARMONY-5532
> > api.text.DecimalFormat_Locales - intermittent(?)
> >
> > • Linux x86 64 bit:
> > vm.classloading.ClassCastTest - failed on M4 too
> > api.kernel.thread.ThreadLocalTest - regression
> >
> > 11) Stress: need investigation
> > • Windows_x86: 1 failure
> > gc.frag.FragmentationFinalizer - intermittent(?)
> >
> > • Linux_x86: 3 failure (failed on M4 too) HARMONY-5159
> > gc.frag.Fragmentation
> > gc.frag.FragmentationFinalizer
> > gc.frag.FragmentationReference
> >
> > • Windows_x86_64: 4 failures
> > classloader.NotSynchThreads.SupIntf - regression
> > gc.frag.FragmentationFinalizer: HARMONY-5159
> > jpda.jdwp.scenario.MEMORY001 - failed on M4 too
> > jpda.jdwp.scenario.MEMORY003 - failed on M4 too
> >
> > • Linux_x86_64: 2 failures
> > jpda.jdwp.scenario.MEMORY001 - failed on M4 too
> > jpda.jdwp.scenario.MEMORY003 - failed on M4 too
> >
> > 12) Struts: HARMONY-5498 is closed but the scenario still fails
> >
> > 13) VTS VM:
> > • Windows_x86_64 & Linux_x86_64
> > vm.jvmti.events.CompiledMethodLoad.CompiledMethodLoad0101
> > HARMONY-5347(regression) won't be fixed in M5
>
>
> --
> Gregory
>
>
>
--
Vladimir Beliaev
Intel Middleware Products Division
Re: [testing] second M5 candidate (r629320) testing status.
Posted by Gregory Shimansky <gs...@apache.org>.
Stepan Mishura said the following on 22.02.2008 8:13:
> Hi all,
>
> Here is r629320 snapshot testing status. Briefly, there are several
> failures: some of them are intermittent and/or known issues (i.e there
> is JIRA for tracking). Also there are several new regressions for
> investigation if they are blockers for M5 or not. I think that the
> most serious one is a crash of Dacapo on Linux'es. Could anyone to
> look into?
>
> Please add your comments and clarifications.
>
> 1) Classlib:
>
> 5 failures in text module because of HARMONY-5465
>
> Status: Tony investigated it - not bug difference?
>
> • Windows_x86_64:
> 1 additional failure in pack200 (not regression)
>
> 2) Dacapo: crash on Linux x86_32 & Linuxs_x86_64 (seems it is not intermittent)
>
> 3) DRLVM regression tests:
> • Windows_x86: org.apache.harmony.drlvm.tests.regression.h5206
This is a bug that was never actually fixed. Looking at it, it was
discovered even in M3. It is an intermittent problem with volatile
fields and it is not a regression.
> 4) DRLVM tests:
> • Windows_x86_64: classloader.StressLoader_jit crash (seems it is not
> intermittent)
>
> Status: according to Vladimir Beliaev this one is not critical and
> should not block the release
>
> 5) EUTs:
> • Windows x86: 3 failures
>
> 6) EGAx48:
> • Windows_x86: failed
> • Linux_x86: in progress (passed on the previous snapshot)
> • Linux x86 64: failed
>
> 7) Eclipse TPTP:
> • Linux_x86_64 - 5 failures: regression
>
> Status: 5 failures (HARMONY-5347), won't be fixed in M5
> + agg_threadPowerWorkload_10_F (new one compared to the
> previous snapshot)
>
> 8) Functional:
> • On all platfroms:
> api.java.security.F_KeyFactoryTest_01:
> HARMONY-4857 - regression introduced in M3. Bug in third-party component
> api.java.beans.beancontext.BeanContextTest
> regression caused by changes in locale data
> api.java.util.jar.Manifest
> regression introduced by the fix of HARMONY-5473
> api.java.text.MessageFormat
> regression caused by migration to ICU HARMONY-5430
>
>
> • Windows_x86: +1 failures
> jit.HLO.devirt.Runtime.RuntimeExtend1 - not regression
>
> • Linux_x86: +4 failures
> functional.org.apache.harmony.test.func.jit.HLO.dce.deadstring
> (intermittent?)
> vm.cli.verbose - regression
> vm.cli.verbose.verbose01 - regression
> vm.cli.Xverbose.Xverbose07 - regression
>
> • Windows_x86_64: +8 failures
> jit.HLO.devirt.Runtime.RuntimeExtend1
> not regression
> jit.HLO.inline.ControlFlow.IfElse.IfElse1
> regression since M3,looked intermittent in M4 but it stably fails
> jit.HLO.peel.Switch -intemittent(?)
> jpda.jdwp.scenario.EB01 - regression
> jpda.jdwp.scenario.ST07 - regression
> reg.vm.btest5717
> regression since M3, looked intermittent in M4 but it stably fails
> reg.vm.btest6353
> failed on M3 too, (Andrey said might be issue with the test)
> reg.vm.btest7214
> regression since M3, looked intermittent in M4 but it stably fails
>
> • Linux_x86_64: +12 failures
> intermittent(?)
> api.java.io.ObjectOutputStream.writeObjectReadObject0010
> api.java.io.ObjectOutputStream.writeObjectReadObject0029
> api.java.io.PushBackInputStream
> api.java.lang.ref.F_PhantomReferenceTest_03
> api.java.lang.ref.F_SoftReferenceTest_03
> api.java.util.logging.Handler
> vm.cli.verbose.verbose
>
> regression:
> jpda.jdwp.scenario.EB01
> jpda.jdwp.scenario.ST07
> reg.jit.btest4318
> vm.cli.verbose.verbose01
>
> reg.vm.btest6353
> failed on M3 too, (Andrey said might be issue with the test?)
>
> 9) Geronimo Unit Tests
>
> • Windows_x86_64: 4 failures
> org.apache.geronimo.cxf - intermittent(?)
>
> • Linux_x86_64: 2 failures
> org.apache.geronimo.cxf - intermittent(?)
>
> 10) Reliability:
>
> • Windows_x86:2 failures
> api.net.DatagramTest - HARMONY-5531
> api.serialization.SerializableClassesTest- HARMONY-5532
>
> • Linux_x86: 3 failures
> api.net.DatagramTest - HARMONY-5531
> api.serialization.SerializableClassesTest- HARMONY-5532
> api.text.DecimalFormat_Locales - intermittent(?)
>
> • Linux x86 64 bit:
> vm.classloading.ClassCastTest - failed on M4 too
> api.kernel.thread.ThreadLocalTest - regression
>
> 11) Stress: need investigation
> • Windows_x86: 1 failure
> gc.frag.FragmentationFinalizer - intermittent(?)
>
> • Linux_x86: 3 failure (failed on M4 too) HARMONY-5159
> gc.frag.Fragmentation
> gc.frag.FragmentationFinalizer
> gc.frag.FragmentationReference
>
> • Windows_x86_64: 4 failures
> classloader.NotSynchThreads.SupIntf - regression
> gc.frag.FragmentationFinalizer: HARMONY-5159
> jpda.jdwp.scenario.MEMORY001 - failed on M4 too
> jpda.jdwp.scenario.MEMORY003 - failed on M4 too
>
> • Linux_x86_64: 2 failures
> jpda.jdwp.scenario.MEMORY001 - failed on M4 too
> jpda.jdwp.scenario.MEMORY003 - failed on M4 too
>
> 12) Struts: HARMONY-5498 is closed but the scenario still fails
>
> 13) VTS VM:
> • Windows_x86_64 & Linux_x86_64
> vm.jvmti.events.CompiledMethodLoad.CompiledMethodLoad0101
> HARMONY-5347(regression) won't be fixed in M5
--
Gregory
Re: [testing] second M5 candidate (r629320) testing status.
Posted by Nellya Udovichenko <ne...@gmail.com>.
Yes. It (1 cxf test) is intermittent fail. No critical and no regression.
It has been excluded but then it has begun to work well so it was removed
from excluded list.
Now I try to reproduce and investigate it locally.
Regards,
Nellya.
On 2/22/08, Stepan Mishura <st...@gmail.com> wrote:
>
>
> 9) Geronimo Unit Tests
>
> • Windows_x86_64: 4 failures
> org.apache.geronimo.cxf - intermittent(?)
>
> • Linux_x86_64: 2 failures
> org.apache.geronimo.cxf - intermittent(?)
>
>
Re: [testing] second M5 candidate (r629320) testing status.
Posted by Andrey Yakushev <an...@gmail.com>.
> 10) Reliability:
>
> • Windows_x86:2 failures
> api.net.DatagramTest - HARMONY-5531
> api.serialization.SerializableClassesTest- HARMONY-5532
>
> • Linux_x86: 3 failures
> api.net.DatagramTest - HARMONY-5531
> api.serialization.SerializableClassesTest- HARMONY-5532
> api.text.DecimalFormat_Locales - intermittent(?)
Yes, it's old known intermittent failure which isn't reproduced
locally. See bottom of
http://wiki.apache.org/harmony/Reliability_Tests_on_DRLVM for details
>
> • Linux x86 64 bit:
> vm.classloading.ClassCastTest - failed on M4 too
HARMONY-5395 - probably gcc bug
> api.kernel.thread.ThreadLocalTest - regression
Similar to DecimalFormat_Locales above
I never ever saw such a small amount of failures for reliability
suite. On M4 we've had ~4-9 failures per platform.
--
Thanks,
Andrey