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

CI failed #1869

Closed
Eskibear opened this issue Sep 6, 2021 · 5 comments · Fixed by #1876
Closed

CI failed #1869

Eskibear opened this issue Sep 6, 2021 · 5 comments · Fixed by #1876
Assignees

Comments

@Eskibear
Copy link
Contributor

Eskibear commented Sep 6, 2021

See https://ci.eclipse.org/ls/job/jdt-ls-pr/2807/ and recent PR builds.

mostly failed cases.

org.eclipse.jdt.ls.core.internal.handlers.CodeActionResolveHandlerTest.testResolveCodeAction_AnnotationQuickFixes
org.eclipse.jdt.ls.core.internal.commands.ProjectCommandTest.testGetClasspathsForMavenWhenUpdating
org.eclipse.jdt.ls.core.internal.commands.ProjectCommandTest.testGetClasspathsForMaven
org.eclipse.jdt.ls.core.internal.handlers.AdvancedOrganizeImportsHandlerTest.testDuplicateStaticImports
org.eclipse.jdt.ls.core.internal.handlers.ResolveSourceMappingHandlerTest.testResolveDependencyUri
org.eclipse.jdt.ls.core.internal.handlers.WorkspaceSymbolHandlerTest.testEmptyNames
org.eclipse.jdt.ls.core.internal.javadoc.JavaDocImageExtractionTest.testImageExtractionWithSourceJar
org.eclipse.jdt.ls.core.internal.managers.MavenBuildSupportTest.testDownloadSources
org.eclipse.jdt.ls.core.internal.managers.MavenBuildSupportTest.testUpdateSnapshots
org.eclipse.jdt.ls.core.internal.managers.MavenProjectImporterTest.testAnnotationProcessing
@rgrunber
Copy link
Contributor

rgrunber commented Sep 7, 2021

This doesn't seem to be consistent : https://ci.eclipse.org/ls/job/jdt-ls-master/ (1157 & 1158 are succeeding).

@snjeza
Copy link
Contributor

snjeza commented Sep 7, 2021

@Eskibear
Copy link
Contributor Author

Eskibear commented Sep 7, 2021

I did observe random failing of PR builds, and I'm curious about what can be the culprit...

Also see:
#1806 (comment)
#1842 (comment) (it's working now after manually retriggering)

@Eskibear
Copy link
Contributor Author

Eskibear commented Sep 8, 2021

https://ci.eclipse.org/ls/job/jdt-ls-pr/2823/console

11:15:46 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:2.3.0:test (default-test) on project org.eclipse.jdt.ls.tests: An unexpected error occurred while launching the test runtime (process returned error code 137(SIGKILL received?)).

seems to be killed after running for 10 min?

@Eskibear
Copy link
Contributor Author

New case of failure:

https://ci.eclipse.org/ls/job/jdt-ls-pr/2838/testReport/org.eclipse.jdt.ls.core.internal.handlers/DocumentLifeCycleHandlerTest/testUnimplementedMethods/

Stacktrace
org.mockito.exceptions.misusing.WrongTypeOfReturnValue: 

Preferences$$EnhancerByMockitoWithCGLIB$$a5cb28e1 cannot be returned by getClientPreferences()
getClientPreferences() should return ClientPreferences
***
If you're unsure why you're getting above error read on.
Due to the nature of the syntax above problem might occur because:
1. This exception *might* occur in wrongly written multi-threaded tests.
   Please refer to Mockito FAQ on limitations of concurrency testing.
2. A spy is stubbed using when(spy.foo()).then() syntax. It is safer to stub spies - 
   - with doReturn|Throw() family of methods. More in javadocs for Mockito.spy() method.

	at org.eclipse.jdt.ls.core.internal.handlers.DocumentLifeCycleHandlerTest.mockPreferences(DocumentLifeCycleHandlerTest.java:198)
	at org.eclipse.jdt.ls.core.internal.handlers.DocumentLifeCycleHandlerTest.setup(DocumentLifeCycleHandlerTest.java:101)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants