Community
Participate
Working Groups
[]: array lengths differed, expected.length=1 actual.length=0; arrays first differed at element [0]; expected:<Type.java:1> but was:<end of array> []: array lengths differed, expected.length=1 actual.length=0; arrays first differed at element [0]; expected:<Type.java:1> but was:<end of array> at org.junit.internal.ComparisonCriteria.arrayEquals(ComparisonCriteria.java:89) at org.junit.internal.ComparisonCriteria.arrayEquals(ComparisonCriteria.java:28) at org.junit.Assert.internalArrayEquals(Assert.java:534) at org.junit.Assert.assertArrayEquals(Assert.java:285) at org.eclipse.jdt.debug.tests.console.JavaStackTraceConsoleTest.testHyperlinkMatchSignatureExtended(JavaStackTraceConsoleTest.java:153) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at junit.framework.TestCase.runTest(TestCase.java:177) at junit.framework.TestCase.runBare(TestCase.java:142) at org.eclipse.jdt.debug.tests.AbstractDebugTest.runBare(
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
