I have updated this morning and I only see 1 consistent failure on
Windows x86 now:
Name Tests
Errors Failures
javax.swing.text.html.HTMLDocument_Reader_ActionsTest
58 1 1
The bad news is that running this test against the M11 build passes for
me, so it's something we have broken since the last milestone. I have
created HARMONY-6392 for these failures.
I see the following test failing about 1 in 10 with a long loop of
repeated output:
org.apache.harmony.jpda.tests.jdwp.MultiSession.RefTypeIDTest
The output looks like:
[SYNC] Waiting for message: continue
java.net.SocketException: The operation timed out
at
org.apache.harmony.luni.platform.OSNetworkSystem.read(OSNetworkSystem.java)
<few more stack lines here snipped>
repeated constantly until the test harness kills it. The [SYNC] message
is from the jpda test framework and I'm suspicious that this timeout
might just be a timing problem with the test case, and the harness is
not handling it properly and entering a loop. I have recreated this
failure on M11 so I don't think it should be a blocker for M12. It looks
like the failure in HARMONY-6388 is the same - I havn't been able to
recreate it but I expect it would fail on M11 also.
I also saw 1 failure/error in each of:
org.apache.harmony.luni.tests.java.io.PipedInputStreamTest
javax.swing.plaf.basic.BasicScrollBarUITest
but running them each standalone 10 times they did not fail again, which
means they are either fairly intermittent, are caused by leftover
artifacts from previous tests or are caused by me using the machine at
the same time as the test run (quite likely).
Regards,
Oliver
Oliver Deakin wrote:
I see 6 failures and 7 errors running on Windows x86 at r883734
Name Tests
Errors Failures
java.awt.WindowTest
7 0 1
javax.swing.ImageIcon_MultithreadedTest
2 0 1
javax.swing.plaf.basic.BasicScrollBarUITest
18 0 1
javax.swing.text.html.HTMLDocument_Reader_ActionsTest
58 1 1
org.apache.harmony.jpda.tests.jdwp.MultiSession.ClassObjectIDTest
1 1 0
org.apache.harmony.jpda.tests.jdwp.MultiSession.RefTypeIDTest
1 1 0
org.apache.harmony.sound.tests.javax.sound.sampled.AudioSystemTest
5 3 2
org.apache.harmony.tests.tools.javac.MainTest
2 1 0
Looks like most of my failures are similar to yours. I think the jpda
tests are intermittent failures that have been known for a while, and
are caused by timeouts which are quite likely to be timing issues in
the tests. I think the java.awt.WindowTest is caused by me moving the
mouse/typing while they were running ;)
I don't see any beans failures.
Regards,
Oliver
Tim Ellison wrote:
I currently see the following 5 failures and 10 errors when testing
r883666
Name Tests Errors Failures
javax.swing 17 0 1
javax.swing.plaf.basic 18 0 1
javax.swing.text.html 58 1 1
org.apache.harmony.jpda.tests.jdwp.DebuggerOnDemand 4 4 0
org.apache.harmony.logging.tests.java.util.logging 13 1 0
org.apache.harmony.sound.tests.javax.sound.sampled 5 3 2
org.apache.harmony.tests.tools.javac 2 1 0
I'll take a look through each and raise JIRAs as appropriate.
I've also re-enabled the full test job on Hudson Ubuntu/x86_64 [1], but
there are a number of beans failures there I don't see locally, which I
am attributing to the fact that the build machine is running on xvfb
[1]
http://hudson.zones.apache.org/hudson/view/Harmony/job/Harmony-1.5-head-linux-x86_64-full-tests/
Regards,
Tim
--
Oliver Deakin
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
