RE: [drlvm][test]Exclude some tests from "build test" target, make 'build test' pass

[Volynets, Vera]

-Original Message-
From: Pavel Ozhdikhin [mailto:[EMAIL PROTECTED] 
Sent: Thursday, October 26, 2006 10:18 AM
To: harmony-dev@incubator.apache.org
Subject: Re: [drlvm][test]Exclude some tests from "build test" target,
make 'build test' pass

On 10/26/06, Gregory Shimansky <[EMAIL PROTECTED]> wrote:
>
> On Wednesday 25 October 2006 21:05 Rana Dasgupta wrote:
> > The ideal way would be for acceptance tests like "build test" to
always
> > pass and to catch and roll back the patch that breaks this
invariant,
> > rather than to disable the tests. But I agree with Vera, it is
important
> to
> > keep a running set up as acceptance tests, so disabling the well
known
> > failures may be the only way until we fix the problems.
> >
> > I don't know that any of the tests are "unstable". These are
> implementation
> > bugs. gc.LOS is a bug in thread yielding by the apr Windows
> functionality.
> > The java.lang.ObjectTest also looks like an interpreter
implementation
> > error.
>
> I wonder about gc.LOS, I remember there was a discussion, and I think
> there
> were patches too. But I cannot find any right now. Were there any
fixes to
> the problem which made gc.LOS to work on WinXP?


This is Harmony-1933
 issue
and it still lacks a patch.

Thanks,
Pavel

Hmm and java.lang.ObjectTest works for me both on windows and linux...
>
> --
> Gregory Shimansky, Intel Middleware Products Division
>

Pavel, test java.lang.ObjectTest fails very seldom. I checked it on Win
XP, ia32, interpreter, release configuration. It didn't fail yesterday
25 October, but it failed 24 October (vm revision: 467401 classlib
revision: 467390) and about a week ago, so it's unstable. 

[drlvm][test]Exclude some tests from "build test" target, make 'build test' pass

[Volynets, Vera]

Geir
Some tests launched by command "build test" fail.
The idea of  "build test" is to run it before each commit. In this way you can 
catch regressions.
In order to effectively catch regressions, i.e. tests that started to fail 
after some change,
it's necessary to have 'build test' pass in a stable way. One of the ways to 
achieve stable state
is to exclude failing tests or tests which show unstable behavior.
So I analysed statistics of test runs on win ia32 platform and made up a list 
of tests to be excluded:
1) smoke
*** gc.LOS fails always on jitrino and interpreter, debug and release
2) kernel
*** java.lang.ClasssGenericsTest and 
*** java.lang.ClassGenericsTest4 fail because of timeout, so I  increase 
timeout in kernel.test.xml
*** java.lang.ObjectTest fail on interpreter with following message:
 Testsuite: java.lang.ObjectTest
 Tests run: 18, Failures: 1, Errors: 0, Time elapsed: 6.109 sec 
 Testcase: testWait1(java.lang.ObjectTest): FAILED
 An InterruptedException must be thrown in test thread!
junit.framework.AssertionFailedError: An InterruptedException must be 
thrown in test thread!
   
See HARNONY-1966 issue with attached patch.


Vera Volynets
Intel Middleware Products Division

[general][svn] which svn revision we take into consideration?

[Volynets, Vera]

Hi,
svn has two commands where you can get svn revision.
It's nice bug the problem is that results are different.
example:
1) svn log --limit 1

r466095 | smishura | 2006-10-20 16:47:14 +0400 (Fri, 20 Oct 2006) | 1 line

Apply patch for HARMONY-1927 ([classlib][tools] 
KeyStoreLoaderSaver.saveStore(..) throws unhandled IllegalArgumentException)

2) svn info 
Path: .
URL: https://svn.apache.org/repos/asf/incubator/harmony/enhanced/classlib/trunk
Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
Revision: 466101
Node Kind: directory
Schedule: normal
Last Changed Author: smishura
Last Changed Rev: 466095
Last Changed Date: 2006-10-20 16:47:14 +0400 (Fri, 20 Oct 2006)
Properties Last Updated: 2006-10-19 15:19:37 +0400 (Thu, 19 Oct 2006)

Could someone explain what the difference between "Revision" and "Last Changed" 
Rev is?
Maybe "Revision" shows current revision which would be "Last Updated" after 
next commit?
Which of these two revisions we call revision?

With best regards, Vera!
Vera Volynets
Intel Middleware Products Division

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [classlib][beans] Failed to build classlib

[Volynets, Vera]

Alexey, Ilya, Tim, Mikhail,
Thank you for advice.
It helped.

With best regards, Vera!

-Original Message-
From: Alexei Zakharov [mailto:[EMAIL PROTECTED] 
Sent: Thursday, October 19, 2006 3:18 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [classlib][beans] Failed to build classlib

Hi Vera,

It seems you have experienced some problems with
classpath/bootclasspath. Try to do "ant clean".

Thanks,

19.10.06, Volynets, Vera<[EMAIL PROTECTED]> написал(а):
>
> Hi,
> I've tried to build classlib today.
> it failed with following message:
> -compile:
>[javac] Since compiler setting isn't classic or modern,ignoring fork 
> setting.
>[javac] Compiling 43 source files to 
> C:\cygwin\work\harmony\trunk\working_classlib\build\classes
>[javac] Since compiler setting isn't classic or modern,ignoring fork 
> setting.
>[javac] --
>[javac] 1. ERROR in 
> C:\cygwin\work\harmony\trunk\working_classlib\modules\beans\src\main\java\java\beans\Encoder.java
>[javac]  (at line 129)
>[javac] if (!Statement.isPDConstructor(oldExp)
>[javac]^^^
>[javac] The method isPDConstructor(Expression) is undefined for the type 
> Statement
>[javac] --
>[javac] 2. ERROR in 
> C:\cygwin\work\harmony\trunk\working_classlib\modules\beans\src\main\java\java\beans\Encoder.java
>[javac]  (at line 130)
>[javac] && !Statement.isStaticMethodCall(oldExp)) {
>[javac]   ^^
>[javac] The method isStaticMethodCall(Expression) is undefined for the 
> type Statement
>[javac] --
>[javac] --
>[javac] 3. ERROR in 
> C:\cygwin\work\harmony\trunk\working_classlib\modules\logging\src\main\java\java\util\logging\Logger.java
>[javac]  (at line 431)
>[javac] Handler handler = 
> (Handler)LogManager.getInstanceByClass(handlerName);
>[javac]   ^^
>[javac] The method getInstanceByClass(String) is undefined for the type 
> LogManager
>[javac] --
>[javac] 3 problems (3 errors)
>
>
> I think this patches could be reason of failure.
> r465186 | mloenko | 2006-10-18 13:28:23 +0400 (Wed, 18 Oct 2006) | 2 lines
>
> applied patch from HARMONY-1529
> [classlib][beans] new fixes for DefaultPersistenceDelegate failures (2)
> 
> r465159 | mloenko | 2006-10-18 10:42:49 +0400 (Wed, 18 Oct 2006) | 3 lines
>
> applied patch from HARMONY-1521
> [classlib][beans] XMLEncoder.writeStatement(null) thorws NPE on Harmony and 
> works OK on RI
> removed redundant method
> 
> r465156 | mloenko | 2006-10-18 10:23:52 +0400 (Wed, 18 Oct 2006) | 2 lines
>
> applied patch from HARMONY-1515
> [classlib][beans] EventSetDescriptor(.., Method) throws 
> IntrospectionException on Harmony end creates object on RI
> 
> r465154 | mloenko | 2006-10-18 10:15:34 +0400 (Wed, 18 Oct 2006) | 2 lines
>
> applied patch from HARMONY-1504
> [classlib][beans] RI throws NPE for public EventSetDescriptor(...) while 
> Harmony does not
> 
> r465152 | mloenko | 2006-10-18 10:00:21 +0400 (Wed, 18 Oct 2006) | 2 lines
>
> applied patch from HARMONY-1304
> [classlib][bean] compatibility: no NPE on Harmony for 
> Encoder().setPersistenceDelegate(Void.TYPE, null)


-- 
Alexei Zakharov,
Intel Enterprise Solutions Software Division, Russia

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[classlib][beans] Failed to build classlib

[Volynets, Vera]

Hi, 
I've tried to build classlib today.
it failed with following message:
-compile:
[javac] Since compiler setting isn't classic or modern,ignoring fork 
setting.
[javac] Compiling 43 source files to 
C:\cygwin\work\harmony\trunk\working_classlib\build\classes
[javac] Since compiler setting isn't classic or modern,ignoring fork 
setting.
[javac] --
[javac] 1. ERROR in 
C:\cygwin\work\harmony\trunk\working_classlib\modules\beans\src\main\java\java\beans\Encoder.java
[javac]  (at line 129)
[javac] if (!Statement.isPDConstructor(oldExp)
[javac]^^^
[javac] The method isPDConstructor(Expression) is undefined for the type 
Statement
[javac] --
[javac] 2. ERROR in 
C:\cygwin\work\harmony\trunk\working_classlib\modules\beans\src\main\java\java\beans\Encoder.java
[javac]  (at line 130)
[javac] && !Statement.isStaticMethodCall(oldExp)) {
[javac]   ^^
[javac] The method isStaticMethodCall(Expression) is undefined for the type 
Statement
[javac] --
[javac] --
[javac] 3. ERROR in 
C:\cygwin\work\harmony\trunk\working_classlib\modules\logging\src\main\java\java\util\logging\Logger.java
[javac]  (at line 431)
[javac] Handler handler = 
(Handler)LogManager.getInstanceByClass(handlerName);
[javac]   ^^
[javac] The method getInstanceByClass(String) is undefined for the type 
LogManager
[javac] --
[javac] 3 problems (3 errors)


I think this patches could be reason of failure.
r465186 | mloenko | 2006-10-18 13:28:23 +0400 (Wed, 18 Oct 2006) | 2 lines

applied patch from HARMONY-1529
[classlib][beans] new fixes for DefaultPersistenceDelegate failures (2)

r465159 | mloenko | 2006-10-18 10:42:49 +0400 (Wed, 18 Oct 2006) | 3 lines

applied patch from HARMONY-1521
[classlib][beans] XMLEncoder.writeStatement(null) thorws NPE on Harmony and 
works OK on RI
removed redundant method

r465156 | mloenko | 2006-10-18 10:23:52 +0400 (Wed, 18 Oct 2006) | 2 lines

applied patch from HARMONY-1515
[classlib][beans] EventSetDescriptor(.., Method) throws IntrospectionException 
on Harmony end creates object on RI

r465154 | mloenko | 2006-10-18 10:15:34 +0400 (Wed, 18 Oct 2006) | 2 lines

applied patch from HARMONY-1504
[classlib][beans] RI throws NPE for public EventSetDescriptor(...) while 
Harmony does not

r465152 | mloenko | 2006-10-18 10:00:21 +0400 (Wed, 18 Oct 2006) | 2 lines

applied patch from HARMONY-1304
[classlib][bean] compatibility: no NPE on Harmony for 
Encoder().setPersistenceDelegate(Void.TYPE, null)

Vera Volynets
Intel Middleware Products Division 

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [classlib][test] Site to collect classlib test statistics

[Volynets, Vera]

Alexey,
You've understood quiet right.
The final goal is to point out bad patch, maybe I'll use bisect
or other algorithm to find this commit.
Anyway I need to collect statistics routinely each day to react fast!
It's good idea to use results of cruise control not to do double work.  

-Original Message-
From: Alexey Varlamov [mailto:[EMAIL PROTECTED] 
Sent: Friday, October 06, 2006 9:32 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [classlib][test] Site to collect classlib test statistics

Vera,

I'm not sure I understood your intention. Do you want to monitor
regressions routinely a la CruiseControl? Or you need an automated
failure analyzer which bisects commits and finds flawed commit?

2006/10/6, Volynets, Vera <[EMAIL PROTECTED]>:
> Alexey,
> Thank you for your response.
> As I understood I'm working on the same problem,
> I write scripts to run different tests(cunit, classlib, smoke, kernel,
> specjvm98) and collect statistics.
> I do it to track patch which was reason of failure of any test. So bug
> propagation would be stopped.
> The final result is presented like table with name and state
> (passed/failed).
> My next step was to use mysql database, php and Apache server to make
my
> system user-friendly. Also I need to think out algorithm to find
> "guilty" revision. Now I run tests only on Windows and only on my
> machine.
> I think it's a good idea to keep in touch and collaborate!
> It's useful to have this system on Harmony,
> because each contributor can see how his patch effect the virtual
> machine!!!
>
> With best regards, Vera!
>
> -Original Message-
> From: Alexey Varlamov [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 06, 2006 4:14 PM
> To: harmony-dev@incubator.apache.org
> Subject: Re: [classlib][test] Site to collect classlib test statistics
>
> Thanks for prompt response!
> Those 554 errors on interpreter are due to fork mode="once", it is a
> single error affecting the whole run. Is there a way to delete an
> uploaded run?
>
> Better yet, to be able select a range of runs to include to analysis.
> The appetite comes with eating :)
> Criteria to select can vary, one of many possible is execution engine
> - it would be nice to have such characteristic of a run ...
>
>
> 2006/10/6, Anton Luht <[EMAIL PROTECTED]>:
> > Alexey,
> >
> > I've added both options - search by test name and list of tests that
> > ever failed. The second one is very big because of results you've
> > uploaded for DRLVM/Linux with 554 errors. Please tell me if you want
> > to change anything in the interface.
> >
> > On 10/6/06, Alexey Varlamov <[EMAIL PROTECTED]> wrote:
> > > Anton,
> > >
> > > Many thanks for exploring this area, it looks quite promising.
> > > An idea: this service would become more valuable if presented
> > > transparent search/comparison of results for particular tests over
> all
> > > uploaded runs.
> > > Let user enter name of a test and show in one table all known
> results
> > > for this test, or even better, provide a table of all ever failed
> > > tests with links to individual consolidated tables.
> > > This would help analyzing failures very much.
> > >
> > > --
> > > Regards,
> > > Alexey
> > >
> > > 2006/10/4, Anton Luht <[EMAIL PROTECTED]>:
> > > > Hello,
> > > >
> > > > > Could you tell about it in more detail?
> > > > > 1) Who can upload test results?
> > > >
> > > > Everyone - no authorization is needed, you can include file
upload
> to
> > > > your regular builds if you want - authorized users can remove
them
> > > > later if something goes wrong :) If you want to modify uploaded
> tests'
> > > > data - add JIRA issues to failures, add comments, etc - please
> send me
> > > > login/password and I'll create an account.
> > > >
> > > > > 2) How are you going to develop this site, structure, data
base
> and
> > > > > etc.?
> > > >
> > > > I'll try to implement all feature requests that community
members
> will
> > > > express. One of possible directions I see is support for new
test
> > > > suites  - currently it  recognises only Harmony  classlib JUnit
> tests
> > > > output. If you have another test suite you want to upload to
that
> site
> > > > - just send me an archive and I'll  try to add support for this
> kind
> > > > of tests.
> > > >
> > &g

RE: [classlib][test] Site to collect classlib test statistics

[Volynets, Vera]

Alexey,
Thank you for your response.
As I understood I'm working on the same problem,
I write scripts to run different tests(cunit, classlib, smoke, kernel,
specjvm98) and collect statistics. 
I do it to track patch which was reason of failure of any test. So bug
propagation would be stopped.
The final result is presented like table with name and state
(passed/failed).  
My next step was to use mysql database, php and Apache server to make my
system user-friendly. Also I need to think out algorithm to find
"guilty" revision. Now I run tests only on Windows and only on my
machine.
I think it's a good idea to keep in touch and collaborate!
It's useful to have this system on Harmony,
because each contributor can see how his patch effect the virtual
machine!!! 

With best regards, Vera!

-Original Message-
From: Alexey Varlamov [mailto:[EMAIL PROTECTED] 
Sent: Friday, October 06, 2006 4:14 PM
To: harmony-dev@incubator.apache.org
Subject: Re: [classlib][test] Site to collect classlib test statistics

Thanks for prompt response!
Those 554 errors on interpreter are due to fork mode="once", it is a
single error affecting the whole run. Is there a way to delete an
uploaded run?

Better yet, to be able select a range of runs to include to analysis.
The appetite comes with eating :)
Criteria to select can vary, one of many possible is execution engine
- it would be nice to have such characteristic of a run ...


2006/10/6, Anton Luht <[EMAIL PROTECTED]>:
> Alexey,
>
> I've added both options - search by test name and list of tests that
> ever failed. The second one is very big because of results you've
> uploaded for DRLVM/Linux with 554 errors. Please tell me if you want
> to change anything in the interface.
>
> On 10/6/06, Alexey Varlamov <[EMAIL PROTECTED]> wrote:
> > Anton,
> >
> > Many thanks for exploring this area, it looks quite promising.
> > An idea: this service would become more valuable if presented
> > transparent search/comparison of results for particular tests over
all
> > uploaded runs.
> > Let user enter name of a test and show in one table all known
results
> > for this test, or even better, provide a table of all ever failed
> > tests with links to individual consolidated tables.
> > This would help analyzing failures very much.
> >
> > --
> > Regards,
> > Alexey
> >
> > 2006/10/4, Anton Luht <[EMAIL PROTECTED]>:
> > > Hello,
> > >
> > > > Could you tell about it in more detail?
> > > > 1) Who can upload test results?
> > >
> > > Everyone - no authorization is needed, you can include file upload
to
> > > your regular builds if you want - authorized users can remove them
> > > later if something goes wrong :) If you want to modify uploaded
tests'
> > > data - add JIRA issues to failures, add comments, etc - please
send me
> > > login/password and I'll create an account.
> > >
> > > > 2) How are you going to develop this site, structure, data base
and
> > > > etc.?
> > >
> > > I'll try to implement all feature requests that community members
will
> > > express. One of possible directions I see is support for new test
> > > suites  - currently it  recognises only Harmony  classlib JUnit
tests
> > > output. If you have another test suite you want to upload to that
site
> > > - just send me an archive and I'll  try to add support for this
kind
> > > of tests.
> > >
> > > Sources of that app are not in SVN now - if you want to
> > > review/fix/improve something - I can send you an archive.
> > > --
> > > Regards,
> > > Anton Luht,
> > > Intel Middleware Products Division
> > >
> > >
-
> > > Terms of use : http://incubator.apache.org/harmony/mailing.html
> > > To unsubscribe, e-mail:
[EMAIL PROTECTED]
> > > For additional commands, e-mail:
[EMAIL PROTECTED]
> > >
> > >
> >
> >
-
> > Terms of use : http://incubator.apache.org/harmony/mailing.html
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail:
[EMAIL PROTECTED]
> >
> >
>
>
> --
> Regards,
> Anton Luht,
> Intel Middleware Products Division
>
> -
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[classlib][test] Site to collect classlib test statistics

[Volynets, Vera]

Anton, 

I found out that you open site http://www.harmonytest.org
 .

As I understood it is used to collect statistics of classlib test
results on different builds.

Could you tell about it in more detail?

 

1) Who can upload test results?

2) How are you going to develop this site, structure, data base and
etc.?

 

Vera Volynets

SSG, MPD/DRL division

VM Development team Intern

Moscow, Russia

+7 495 545-3710 ext. 3906

 

 

RE: Re: [DRLVM] GC heap verification infrastructure

[Volynets, Vera]

Hi, 
I didn't find any bugs in gc_v4 at the moment,
but this feature is really very useful especially if
you modify gc_v4 or design a new gc. Of course, it needs to 
be improved and developed.

Also I'm going to add feature to verify write barriers work. 
The same way as in GC heap verification I use idea to
hijack interface function concerning write barriers.

This patch will be sent a bit later.

Pleased to hear from you, Vera :)!
 
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Egor Pasko
Sent: Saturday, July 15, 2006 9:37 AM
To: harmony-dev@incubator.apache.org
Subject: Re: [DRLVM] GC heap verification infrastructure

On the 0x1A6 day of Apache Harmony Vera Volynets wrote:
> *   GC heap verification infrastructure   *** 
> Hi,
> I have been working on implementing GC heap verification
infrastructure
> for Stop-The-World GC in DRLVM.
> This infrastructure is intended be used with any stop-the-world GC
> implementation, conforming to the GC-VM interface (described in gc.h
and
> vm_gc.h), with only a minor GC-VM interface change. 
> It works on Windows and Linux ia32 platforms.

cool feature! did you find any bugs in DRLVM while testing?
do you have plans/ideas for future development of the tool?

> [...]
>  
> *Patch contents*
> This is an individual contribution, and it was prepared according to
the
> requirements of Apache cleanroom process; the size of two files all in
> all is about 30kb (161 and 585 lines). 
> -Patch Add-function-to-gc-interface.txt

oh, I found it! HARMONY-881 

-- 
Egor Pasko, Intel Managed Runtime Division


-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[DRLVM] GC heap verification infrastructure

[Volynets, Vera]

*   GC heap verification infrastructure   *** 
Hi,
I have been working on implementing GC heap verification infrastructure
for Stop-The-World GC in DRLVM.
This infrastructure is intended be used with any stop-the-world GC
implementation, conforming to the GC-VM interface (described in gc.h and
vm_gc.h), with only a minor GC-VM interface change. 
It works on Windows and Linux ia32 platforms.
 
*Description*
GC heap verification infrastructure is a small module which is hijacked
into GC-VM interface.
The main idea is to substitute GC interface function so that necessary
information can be easily collected.
 
Everybody who is interested in GC development and debugging is invited
to try it, modify files and add their own functionality.
 
At this moment GC heap verification infrastructure verifies that the
structure of object reference graph stays exactly the same during
collection. Therefore, the number of strongly reachable live objects and
live bytes before and after GC should stay unchanged.
 
The verification is performed in two phases:
1) On the start of Stop-The-World phase, all enumerated roots to GC by
VM are cached by GC heap verification infrastructure and heap is
traversed, constructing heap "fingerprint", recording the order of the
objects and counting their number and size.   
2) After actual garbage collection is complete, before resuming user
threads, the heap is traced once again and the heap structure is
verified. 
 
*Patch contents*
This is an individual contribution, and it was prepared according to the
requirements of Apache cleanroom process; the size of two files all in
all is about 30kb (161 and 585 lines). 
-Patch Add-function-to-gc-interface.txt
It adds function gc_add_finalizable_root_set_entry() for separate
counting of finalizable objects because the GC may not preserve ordering
of finalizable objects, and thus the heap structure can be changed.
 
-Patch Checks-correctness-of-gc-work.txt
The heart of this patch is file gc_debug.cpp.
The tracing of heap starts with debug_gc_trace_heap() function.
 
*Users guide*
The debugging mode is off by default, and has no impact on the GC
performance.. 
- To turn on GC Debug infrastructure use VM with -Dvm.verify.gc=true
option in command line.
- To see debug information build VM in debug mode, BUILD_CFG=debug, and
use logger in usual way.
When enabled, the verification heap trace takes quite a bit of time (two
times for each collection: before and after actual collection), GC
pauses increase by 1.5-2 times (from 1406ms to 2515ms) when running
Eclipse on DRLVM built in debug configuration.   
--
Vera Volynets, Intel Middleware Products Division

-
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]