4.2 tests status
Locked
 
|
We're down to just the following failing tests (2202 VM):
1 CompilerExceptionsTest>>#testUnusedVariable 2 DecompilerTests>>#testDecompilerInClassesMAtoMM 3 DecompilerTests>>#testDecompilerInClassesSNtoSZ 4 ExceptionTests>>#testHandlerFromAction 5 MirrorPrimitiveTests>>#testMirrorAt 6 MirrorPrimitiveTests>>#testMirrorInstVarAt 7 ProcessTest>>#testAtomicSuspend 8 StandardSystemFontsTest>>#testRestoreDefaultFonts This is the list when run with the latest Cog VM: 1 CompilerExceptionsTest>>#testUnusedVariable 2 DecompilerTests>>#testDecompilerInClassesMAtoMM 3 DecompilerTests>>#testDecompilerInClassesSNtoSZ 4 ExceptionTests>>#testHandlerFromAction 9 FileStreamTest>>#testPositionPastEndIsAtEnd 10 MorphicUIBugTest>>#testShowAllBinParts 1, 4, 5, 6 and 9 are VM-related and cannot be fixed for 4.2. Levente said he would integrate fixes for 2 and 3 from the Inbox. 10 has a very strange failure on the Cog VM for which I will post details in a separate message. That leaves just 7 and 8 which only fail on the 2202 VM, but work on the Cog VM. We're almost there! - Chris |
|
|
On Thu, 20 Jan 2011, Chris Muller wrote:
> We're down to just the following failing tests (2202 VM): > > 1 CompilerExceptionsTest>>#testUnusedVariable > 2 DecompilerTests>>#testDecompilerInClassesMAtoMM > 3 DecompilerTests>>#testDecompilerInClassesSNtoSZ > 4 ExceptionTests>>#testHandlerFromAction > 5 MirrorPrimitiveTests>>#testMirrorAt > 6 MirrorPrimitiveTests>>#testMirrorInstVarAt > 7 ProcessTest>>#testAtomicSuspend > 8 StandardSystemFontsTest>>#testRestoreDefaultFonts > > This is the list when run with the latest Cog VM: > > 1 CompilerExceptionsTest>>#testUnusedVariable > 2 DecompilerTests>>#testDecompilerInClassesMAtoMM > 3 DecompilerTests>>#testDecompilerInClassesSNtoSZ > 4 ExceptionTests>>#testHandlerFromAction > 9 FileStreamTest>>#testPositionPastEndIsAtEnd This one is passing for me. > 10 MorphicUIBugTest>>#testShowAllBinParts > > 1, 4, 5, 6 and 9 are VM-related and cannot be fixed for 4.2. Levente 1 is a Compiler bug, but it requires a lot of work to fix. 4 is also a bug in the image, though it may require VM changes to fix it. > said he would integrate fixes for 2 and 3 from the Inbox. Right I'll do that as soon as I'm ready with the stdio changes/fixes, which I'd like to push to 4.2. > > 10 has a very strange failure on the Cog VM for which I will post > details in a separate message. > > That leaves just 7 and 8 which only fail on the 2202 VM, but work on the Cog VM. 7 is a VM bug IIRC. Do you know why is 8 failing? Levente > > We're almost there! > > - Chris > > |
|
|
On 1/20/2011 6:53 PM, Levente Uzonyi wrote:
> On Thu, 20 Jan 2011, Chris Muller wrote: > >> We're down to just the following failing tests (2202 VM): >> >> 1 CompilerExceptionsTest>>#testUnusedVariable >> 2 DecompilerTests>>#testDecompilerInClassesMAtoMM >> 3 DecompilerTests>>#testDecompilerInClassesSNtoSZ >> 4 ExceptionTests>>#testHandlerFromAction >> 5 MirrorPrimitiveTests>>#testMirrorAt >> 6 MirrorPrimitiveTests>>#testMirrorInstVarAt >> 7 ProcessTest>>#testAtomicSuspend >> 8 StandardSystemFontsTest>>#testRestoreDefaultFonts >> >> This is the list when run with the latest Cog VM: >> >> 1 CompilerExceptionsTest>>#testUnusedVariable >> 2 DecompilerTests>>#testDecompilerInClassesMAtoMM >> 3 DecompilerTests>>#testDecompilerInClassesSNtoSZ >> 4 ExceptionTests>>#testHandlerFromAction >> 9 FileStreamTest>>#testPositionPastEndIsAtEnd > > This one is passing for me. > >> 10 MorphicUIBugTest>>#testShowAllBinParts >> >> 1, 4, 5, 6 and 9 are VM-related and cannot be fixed for 4.2. Levente > > 1 is a Compiler bug, but it requires a lot of work to fix. 4 is also a > bug in the image, though it may require VM changes to fix it. I think 4 can be fixed from the image but since my first attempt was too naive we shouldn't wait for it. I vote for declaring it an expected failure until we've figured out how to deal with it properly. 5-7 are probably just missing in VMMaker. I would coordinate with David to see if we can get these into the interpreter (#7 actually *is* in VMMaker but no VMs have been built with it). > 7 is a VM bug IIRC. Do you know why is 8 failing? See above for 7. 8, I suspect, may be a side effect of running tests in a particular order. Cheers, - Andreas |
|
|
On Thu, Jan 20, 2011 at 11:23:15PM +0100, Andreas Raab wrote:
> On 1/20/2011 6:53 PM, Levente Uzonyi wrote: > >On Thu, 20 Jan 2011, Chris Muller wrote: > > > >>We're down to just the following failing tests (2202 VM): > >> > >>1 CompilerExceptionsTest>>#testUnusedVariable > >>2 DecompilerTests>>#testDecompilerInClassesMAtoMM > >>3 DecompilerTests>>#testDecompilerInClassesSNtoSZ > >>4 ExceptionTests>>#testHandlerFromAction > >>5 MirrorPrimitiveTests>>#testMirrorAt > >>6 MirrorPrimitiveTests>>#testMirrorInstVarAt > >>7 ProcessTest>>#testAtomicSuspend > >>8 StandardSystemFontsTest>>#testRestoreDefaultFonts > >> > >>This is the list when run with the latest Cog VM: > >> > >>1 CompilerExceptionsTest>>#testUnusedVariable > >>2 DecompilerTests>>#testDecompilerInClassesMAtoMM > >>3 DecompilerTests>>#testDecompilerInClassesSNtoSZ > >>4 ExceptionTests>>#testHandlerFromAction > >>9 FileStreamTest>>#testPositionPastEndIsAtEnd > > > >This one is passing for me. > > > >>10 MorphicUIBugTest>>#testShowAllBinParts > >> > >>1, 4, 5, 6 and 9 are VM-related and cannot be fixed for 4.2. Levente > > > >1 is a Compiler bug, but it requires a lot of work to fix. 4 is also a > >bug in the image, though it may require VM changes to fix it. > > I think 4 can be fixed from the image but since my first attempt was too > naive we shouldn't wait for it. I vote for declaring it an expected > failure until we've figured out how to deal with it properly. > > 5-7 are probably just missing in VMMaker. I would coordinate with David > to see if we can get these into the interpreter (#7 actually *is* in > VMMaker but no VMs have been built with it). I took a look at the mirror primitives a couple of weeks ago, and I'm afraid it is a bit beyond my abilities to integrate them. Eliot may have some further updates in the works, but aside from that I would say that we should call it an expected failure for the interpreter VM. Dave > > >7 is a VM bug IIRC. Do you know why is 8 failing? > > See above for 7. 8, I suspect, may be a side effect of running tests in > a particular order. > > Cheers, > - Andreas |
|
|
In reply to this post by Andreas.Raab
Which means there's a bug in at least one test. Tests shouldn't affect the results of other tests. If any one has any idea which test(s) are leaving such dirt behind, I'd very much appreciate being pointed in the right direction; I care enough about this to do something about it if I can, but probably not in time for this release.
On Jan 20, 2011, at 2:23 PM, Andreas Raab <[hidden email]> wrote: > See above for 7. 8, I suspect, may be a side effect of running tests in a particular order. > > Cheers, > - Andreas > |
«
Return to Squeak - Dev
|
1 view|%1 views
| Free forum by Nabble | Edit this page |