I can see the failures started with commit r644719 which commit patch for HARMONY-5684 about native memory management and tuning. Any idea about that?
On 8/1/08, chunrong lai <[EMAIL PROTECTED]> wrote: > > > Hmm. The failures are also in M6. > http://people.apache.org/~smishura/r653525/Windows_x86/classlib-test/ > http://people.apache.org/~smishura/r653525/Linux_x86_64/classlib-test/ > > > On 8/1/08, chunrong lai <[EMAIL PROTECTED]> wrote: >> >> >> I can see the failures in r674840. I guess the failure started earlier. >> I'd like to figure it out. Thanks. >> http://people.apache.org/~chunrong/snapshots/r674840/index.html >> >> >> On 7/31/08, Tim Ellison <[EMAIL PROTECTED]> wrote: >>> >>> We are down to two failures in the classlib tests on windows according to >>> >>> >>> http://people.apache.org/~chunrong/harmony-integrity/windows_x86/classlib-test/ >>> >>> I don't see those failing when using the IBM VM. Any DRLVMers notice >>> when this started failing? >>> >>> Thanks, >>> Tim >>> >>> chunrong lai wrote: >>> >>>> Hi, >>>> >>>> Should we freeze the code base for M7, since the Jul. 28th is said to >>>> be >>>> the code freeze date? >>>> If so, I think >>>> (1) We should follow Tim's policy "no more commits please without >>>> agreement from two committers on the dev list" before code unfrozen. >>>> (2) We need to nominate the M7 candidate revision, do more testing, >>>> analyze the critical/blocker issues and raise the issues MUST be fixed >>>> for >>>> M7. >>>> >>>> Thanks. >>>> Chunrong Lai >>>> Intel System Software Division >>>> >>>> >> >
