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

Random failing ClasspathTests.testExternalJarRemove #3352

Open
jukzi opened this issue Nov 26, 2024 · 0 comments
Open

Random failing ClasspathTests.testExternalJarRemove #3352

jukzi opened this issue Nov 26, 2024 · 0 comments
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 26, 2024

junit.framework.ComparisonFailure: Unexpected markers.
----------- Expected ------------
Project 'P' is missing required library: '/home/jenkins/agent/workspace/AutomatedTests/ep435I-unit-linux-x86_64-java21/workarea/I20241126-0110/eclipse-testing/test-eclipse/eclipse/jdt_model_folder/test185733.jar'
------------ but was ------------
Archive for required library: '/home/jenkins/agent/workspace/AutomatedTests/ep435I-unit-linux-x86_64-java21/workarea/I20241126-0110/eclipse-testing/test-eclipse/eclipse/jdt_model_folder/test185733.jar' in project 'P' cannot be read or is not a valid ZIP file
---------------------- ----------
expected:<[Project 'P' is missing required library: '/home/jenkins/agent/workspace/AutomatedTests/ep435I-unit-linux-x86_64-java21/workarea/I20241126-0110/eclipse-testing/test-eclipse/eclipse/jdt_model_folder/test185733.jar']> but was:<[Archive for required library: '/home/jenkins/agent/workspace/AutomatedTests/ep435I-unit-linux-x86_64-java21/workarea/I20241126-0110/eclipse-testing/test-eclipse/eclipse/jdt_model_folder/test185733.jar' in project 'P' cannot be read or is not a valid ZIP file]>
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.AbstractJavaModelTests.assertMarkers(AbstractJavaModelTests.java:1062)
at org.eclipse.jdt.core.tests.model.AbstractJavaModelTests.assertBuildPathMarkers(AbstractJavaModelTests.java:1030)
at org.eclipse.jdt.core.tests.model.ClasspathTests.testExternalJarRemove(ClasspathTests.java:3200)
at java.base/java.lang.reflect.Method.invoke(Method.java:580)
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)

https://download.eclipse.org/eclipse/downloads/drops4/I20241126-0110/testresults/html/org.eclipse.jdt.core.tests.model_ep435I-unit-linux-x86_64-java21_linux.gtk.x86_64_21.html

@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 26, 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 test Work on unit tests, no change of productive code
Projects
None yet
Development

No branches or pull requests

1 participant