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

[build][test] ClasspathTests.testDotDotLibraryEntry7 failure #3093

Open
mpalat opened this issue Oct 16, 2024 · 2 comments
Open

[build][test] ClasspathTests.testDotDotLibraryEntry7 failure #3093

mpalat opened this issue Oct 16, 2024 · 2 comments
Labels
build test failure Unit Test failures in builds - maynot be a regression caused by the previous change

Comments

@mpalat
Copy link
Contributor

mpalat commented Oct 16, 2024

At: https://download.eclipse.org/eclipse/downloads/drops4/I20241015-1820/testresults/html/org.eclipse.jdt.core.tests.model_ep434I-unit-macM1-java17_macosx.cocoa.aarch64_17.html

org.eclipse.jdt.core.tests.model.ClasspathTests | testDotDotLibraryEntry7 | Error |

/Users/genie.releng/workspace/AutomatedTests/ep434I-unit-macM1-java17/workarea/I20241015-1820/eclipse-testing/test-eclipse/Eclipse.app/Contents/Eclipse/jdt_model_folder/jclMin1.8.jar is not on its project's build path

Java Model Exception: Error in Java Model (code 1006): /Users/genie.releng/workspace/AutomatedTests/ep434I-unit-macM1-java17/workarea/I20241015-1820/eclipse-testing/test-eclipse/Eclipse.app/Contents/Eclipse/jdt_model_folder/jclMin1.8.jar is not on its project's build pathat org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:556)at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:234)at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:569)at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:292)at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:278)at org.eclipse.jdt.internal.core.JavaElement.getChildren(JavaElement.java:233)at org.eclipse.jdt.core.tests.model.ModifyingResourceTests.expandAll(ModifyingResourceTests.java:223)at org.eclipse.jdt.core.tests.model.ModifyingResourceTests.expandAll(ModifyingResourceTests.java:229)at org.eclipse.jdt.core.tests.model.ModifyingResourceTests.expandAll(ModifyingResourceTests.java:215)at org.eclipse.jdt.core.tests.model.ModifyingResourceTests.assertElementDescendants(ModifyingResourceTests.java:103)at org.eclipse.jdt.core.tests.model.ClasspathTests.testDotDotLibraryEntry7(ClasspathTests.java:2818)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)
-- | -- | -- | --

@mpalat mpalat added the build test failure Unit Test failures in builds - maynot be a regression caused by the previous change label Oct 16, 2024
@mpalat mpalat changed the title [build][test] testDotDotLibraryEntry7 failure [build][test] ClasspathTests.testDotDotLibraryEntry7 failure Oct 16, 2024
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
Projects
None yet
Development

No branches or pull requests

2 participants