Re: Mauve regressions (Was: [cp-patches] FYI: Component.setName() fix)
Hi Mark, list. On Wed, 2006-07-26 at 23:09 +0200, Mark Wielaard wrote: Regressions: snip FAIL: java.math.BigDecimal.DiagBigDecimal FAIL: java.math.BigDecimal.construct FAIL: java.math.BigDecimal.setScale FWIW I think these were introduced in the BigDecimal merge from generics branch as noted on cp-patches at the time [1]. Doesn't help resolve but at least pinpoints where they crept in. Paul [1] http://developer.classpath.org/pipermail/classpath-patches/2006-June/002553.html -- Paul Jenner [EMAIL PROTECTED]
Re: Mauve regressions (Was: [cp-patches] FYI: Component.setName() fix)
On Wed, 2006-07-26 at 17:33 -0400, Tom Tromey wrote: I thought the builder was running xvfb so that the AWT tests were isolated on their own X server... ? I usually run the tests directly from the command line, a la jamvm Harness -debug -showpasses -vm jamvm gnu/testlet/java/awt/Robot I believe Mark also ran the tests locally, as the builder hasn't picked up some recent changes to Mauve. Those tests might (probably will?) show up as passes on the builder too. Francis
Re: Mauve regressions (Was: [cp-patches] FYI: Component.setName() fix)
Hi, Running off the latest HEAD, the following pass on my machine: FAIL: java.awt.Component.keyPressTest FAIL: java.awt.FileDialog.TestGraphics FAIL: java.awt.Robot.keyPress FAIL: java.awt.Robot.keyRelease FAIL: java.awt.Robot.mouseMove FAIL: java.awt.Robot.mousePress FAIL: java.awt.Robot.mouseRelease FAIL: java.awt.Robot.mouseWheel FAIL: java.awt.Scrollbar.ScrollbarPaintTest FAIL: java.awt.TextArea.ScrollbarPaintTest FAIL: java.awt.TextComponent.ignoreOldMouseEvents FAIL: java.lang.InheritableThreadLocal.simple FAIL: javax.swing.RepaintManager.addDirtyRegion (Roman just fixed this) Most of those tests use the Robot in some way, and I've noticed that tests using the robot require that the computer be dedicated solely to the tests... running it in the background while doing other work can cause the tests to return incorrect results. Anyways, that narrows down the list a bit if those tests do indeed pass =) Francis
Re: Mauve regressions (Was: [cp-patches] FYI: Component.setName() fix)
Francis == Francis Kung [EMAIL PROTECTED] writes: Francis Most of those tests use the Robot in some way, and I've Francis noticed that tests using the robot require that the computer Francis be dedicated solely to the tests... running it in the Francis background while doing other work can cause the tests to Francis return incorrect results. I thought the builder was running xvfb so that the AWT tests were isolated on their own X server... ? Tom
Re: Mauve regressions (Was: [cp-patches] FYI: Component.setName() fix)
Mark == Mark Wielaard [EMAIL PROTECTED] writes: Mark The results aren't that. bad (all generated against cacao on fc5 x86-64) Mark Lots of new PASSes. One new fail: I don't think new fails matter much. I tend to ignore them myself; I think they're also ignored for the purpose of baseline computation. Mark FAIL: java.lang.InheritableThreadLocal.simple I updated Classpath and Mauve and ran this test case in my Eclipse workspace -- everything passed. Tom
Re: Mauve regressions (Was: [cp-patches] FYI: Component.setName() fix)
Hi, On Wed, 2006-07-26 at 17:33 -0400, Tom Tromey wrote: Mark FAIL: java.lang.InheritableThreadLocal.simple I updated Classpath and Mauve and ran this test case in my Eclipse workspace -- everything passed. Same here now for both jamvm and cacao when run just this test. But sometimes when I run all of the lang tests I can sometimes get it to fail with cacao. So this might be a cacao specific issue. Cheers, Mark
Re: Mauve regressions (Was: [cp-patches] FYI: Component.setName() fix)
Hi, On Wed, 2006-07-26 at 17:48 -0400, Francis Kung wrote: I believe Mark also ran the tests locally, as the builder hasn't picked up some recent changes to Mauve. Those tests might (probably will?) show up as passes on the builder too. Yes, those were my local ran tests. Rerunning them a couple of times by hand and making sure nothing else is running they do indeed PASS. Builder hasn't completed a new run with the new Harness yet. I cleared the previous baselines to get a fresh start (the old ones had a couple of test results with trailing ':' characters which confused the comparison). Cheers, mark
