harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiao-Feng Li" <xiaofeng...@gmail.com>
Subject Re: [general] Reminder: stable build goal at end of month
Date Sat, 21 Apr 2007 04:08:13 GMT
Do we want to switch tomorrow or on Monday for a one-week trial? The
test results last night showed GCv5 has reasonable stability now. Many
thanks to Vladimir A Ivanov for the testing infrastructure.

>From the testing logs at http://www.harmonytest.org/upload/cc2.html,
we can see there are only a couple of test case failures in all the
platforms with all the execution modes. Some of the failures are
occasional actually, especially those with finalizer.

Below is a summary of the testing status:
Linux 32bit: all passed.
Linux 64bit: only one case failure: gc.RunFinalizersOnExitTest (interpreter)
Windows 32bit: only one case failure: exception.FinalizeStackTest (opt/srv)
Windows 64bit: more test failures. Some are abnormal that we didn't met before.

All the failure cases will be checked.

(Note GCv4.1 sometimes fails with some test cases as well.)


On 4/18/07, Xiao-Feng Li <xiaofeng.li@gmail.com> wrote:
> GCv5 might be one "major" that we want to put as default GC in DRLVM.
> It still has some issues pending, but overall I think the stability is
> good enough for a switch next week.
> Since GC is designed with good modularity, we can simply choose which
> GC implementation to use in command line with
> '-XX:vm.dlls=the_gc_module.dll(so)". This is neat that helps the
> switch a lot: If GCv5 has some problem running a workload, we can
> specify -XX:vm.dlls=gc_cc.dll in command line.
> So far the known bugs in GCv5 are not with some workloads, but related
> with certain test cases for finalizer and VM threading. And I think
> they are going to be resolved before next week.
> Thanks,
> xiaofeng
> On 4/16/07, Tim Ellison <t.p.ellison@gmail.com> wrote:
> > Just a reminder, as discussed in various threads, we shall aim to
> > produce a solid build for Windows and Linux x86 (at least) at the end of
> >  next week; so that we have something to demo at ApacheCon and JavaOne
> > that is a true reflection of our current capabilities.
> >
> > Of course, the Milestone will be simply a snapshot, carrying our usual
> > caveats.  The idea is that with conference talks taking place we may
> > expect a few people to download a build and try it around that time, so
> > being in the middle of a major restructuring would potentially do us an
> > injustice.
> >
> > Most commits still seem to be on-going bug fixing, so that's all
> > goodness.  If you are planning on anything 'major' please ensure there
> > is enough time to get it stable, or please wait until after the
> > milestone build.  Similarly, if there is anything that is currently
> > 'broken' that you think really needs fixing for that stability, please
> > shout here on the list.
> >
> > There are still two weeks to go, I think the paranoia about not causing
> > regressions will really kick-in next week :-)
> >
> > Regards,
> > Tim
> >
> --
> http://xiao-feng.blogspot.com


View raw message