Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

31 Random failing JavadocBugsCompletionModelTest, JavadocFieldCompletionModelTest, JavadocMethodCompletionModelTest #3325

Open
jukzi opened this issue Nov 19, 2024 · 1 comment
Labels
build test failure Unit Test failures in builds - maynot be a regression caused by the previous change test Work on unit tests, no change of productive code

Comments

@jukzi
Copy link
Contributor

jukzi commented Nov 19, 2024

https://download.eclipse.org/eclipse/downloads/drops4/I20241118-1800/testresults/html/org.eclipse.jdt.core.tests.model_ep434I-unit-linux-x86_64-java17_linux.gtk.x86_64_17.html
for example:

junit.framework.ComparisonFailure: Completion proposals are not correct!.
----------- Expected ------------
Object[JAVADOC_TYPE_REF]{{@link Object}, java.lang, Ljava.lang.Object;, null, null, [46, 49], 85}\n
Object[TYPE_REF]{Object, java.lang, Ljava.lang.Object;, null, null, [46, 49], 54}
------------ but was ------------

---------------------- ----------
expected:<[Object[JAVADOC_TYPE_REF]{{@link Object}, java.lang, Ljava.lang.Object;, null, null, [46, 49], 85}\n
Object[TYPE_REF]{Object, java.lang, Ljava.lang.Object;, null, null, [46, 49], 54}]> but was:<[]>
at org.eclipse.jdt.core.tests.junit.extension.TestCase.assertStringEquals(TestCase.java:265)
at org.eclipse.jdt.core.tests.junit.extension.TestCase.assertEquals(TestCase.java:240)
at org.eclipse.jdt.core.tests.model.AbstractJavadocCompletionModelTest.assertResults(AbstractJavadocCompletionModelTest.java:283)
at org.eclipse.jdt.core.tests.model.AbstractJavadocCompletionModelTest.assertSortedResults(AbstractJavadocCompletionModelTest.java:253)
at org.eclipse.jdt.core.tests.model.JavadocBugsCompletionModelTest.testBug117183c(JavadocBugsCompletionModelTest.java:653)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at junit.framework.TestCase.runTest(TestCase.java:177)
at org.eclipse.jdt.core.tests.junit.extension.TestCase.runTest(TestCase.java:970)
at junit.framework.TestCase.runBare(TestCase.java:142)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:130)
at junit.framework.TestSuite.runTest(TestSuite.java:241)
at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$Suite.runTest(SuiteOfTestCases.java:114)
at junit.framework.TestSuite.run(TestSuite.java:236)
at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$Suite.superRun(SuiteOfTestCases.java:97)
at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$Suite$1.protect(SuiteOfTestCases.java:85)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$Suite.run(SuiteOfTestCases.java:94)
at junit.framework.TestSuite.runTest(TestSuite.java:241)
at junit.framework.TestSuite.run(TestSuite.java:236)
at junit.framework.TestSuite.runTest(TestSuite.java:2
@jukzi jukzi added test Work on unit tests, no change of productive code build test failure Unit Test failures in builds - maynot be a regression caused by the previous change labels Nov 19, 2024
@jukzi
Copy link
Contributor Author

jukzi commented Nov 19, 2024

Can not locally reproduce [win]. => probably some race condition.
https://download.eclipse.org/eclipse/downloads/drops4/I20241118-1800/testresults/ep434I-unit-linux-x86_64-java17_linux.gtk.x86_64_17/org.eclipse.jdt.core.tests.model.AllJavaModelTests.txt contains 435 times "Exception" - hard to tell which of them are intended or the possible rootcause.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build test failure Unit Test failures in builds - maynot be a regression caused by the previous change test Work on unit tests, no change of productive code
Projects
None yet
Development

No branches or pull requests

1 participant