I think it is fine to simply exclude the test for now. It can be
re-enabled whenever the issue is resolved in javac.
-Chris.
On 02/14/2013 11:17 AM, Maurizio Cimadamore wrote:
If we really care about running the test, javac has an hidden flag that
can be used to force the old inference scheme (I left that as an
emergency hatch in cases like these) - so I believe the test can be
compiled by using
-XDuseLegacyInference
That will essentially force a JDK 7-like behavior of type-inference -
not really recommended if the source contains JDK 8 features such as
lambda expressions - but it's not the case here.
Maurizio
On 14/02/13 11:11, Chris Hegarty wrote:
This test started failing since the integration of new inference
scheme in javac [1]. The javac issue is being tracked by 8008200, so I
am simply proposing to add this test to the ProblemList until the
underlying issue can be resolved.
>: hg diff ProblemList.txt
diff -r e6f34051c60c test/ProblemList.txt
--- a/test/ProblemList.txt Wed Feb 13 16:15:09 2013 -0500
+++ b/test/ProblemList.txt Thu Feb 14 11:11:05 2013 +0000
@@ -133,6 +133,9 @@ java/lang/management/MemoryMXBean/ResetP
# 7196801
java/lang/management/MemoryMXBean/LowMemoryTest2.sh generic-all
+
+# 8008200
+java/lang/Class/asSubclass/BasicUnit.java generic-all
############################################################################
-Chris.
[1] http://hg.openjdk.java.net/jdk8/tl/langtools/rev/2154ed9ff6c8
