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

[Java][CI] AMD64 Debian 12 Complete Documentation CI Failure #43378

Closed
vibhatha opened this issue Jul 23, 2024 · 9 comments
Closed

[Java][CI] AMD64 Debian 12 Complete Documentation CI Failure #43378

vibhatha opened this issue Jul 23, 2024 · 9 comments

Comments

@vibhatha
Copy link
Collaborator

Describe the bug, including details regarding any error messages, version, and platform.

A Java CI failure occurs consistently: https://github.com/apache/arrow/actions/runs/10044510644/job/27759718384?pr=43363#step:7:15698

[INFO] 30 goals, 30 executed
Error:  Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.12.1:site (default-site) on project arrow-java-root: failed to get report for org.apache.maven.plugins:maven-javadoc-plugin: Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.4.1:enforce (enforce-maven-version) on project arrow-bom: Execution enforce-maven-version of goal org.apache.maven.plugins:maven-enforcer-plugin:3.4.1:enforce failed: Unable to provision, see the following errors:
Error:  
Error:  1) Error in custom provider, com.google.inject.OutOfScopeException: No MavenProject is executing on this thread.
Error:    at ClassRealm[coreExtension>com.gradle:develocity-maven-extension:1.21.5, parent: ClassRealm[plexus.core, parent: null]] (via modules: org.eclipse.sisu.wire.WireModule -> org.eclipse.sisu.plexus.PlexusBindingModule -> com.gradle.maven.extension.b -> com.gradle.maven.extension.b$a -> com.gradle.maven.cache.extension.h.a)
Error:    while locating com.gradle.maven.cache.extension.d.k
Error: [ERROR] 
Error: [ERROR] 1 error
Error:  -> [Help 1]
Error:  
Error:  To see the full stack trace of the errors, re-run Maven with the -e switch.
Error:  Re-run Maven using the -X switch to enable full debug logging.
Error:  
Error:  For more information about the errors and possible solutions, please read the following articles:
Error:  [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Error:  
Error:  After correcting the problems, you can resume the build with the command
Error:    mvn <args> -rf :arrow-java-root

Component(s)

Integration

@danepitkin
Copy link
Member

danepitkin commented Aug 1, 2024

FWIW, I've seen this fail a couple times a week ago. I think its an intermittent issue. The Gradle develocity plugin does some sort of network communication, so maybe this job is not configured to fail gracefully while our other jobs are?

@laurentgo
Copy link
Collaborator

I didn't find anything remotely close on the gradle community forums. ge.apache.org has experienced some stability issues in the recent weeks, no idea if related or not

@vibhatha
Copy link
Collaborator Author

vibhatha commented Aug 1, 2024

Thanks for looking into this @danepitkin and @laurentgo

I will check further.

@kou
Copy link
Member

kou commented Aug 12, 2024

This failure is still happening:

https://github.com/apache/arrow/actions/runs/10356219911/job/28665598777#step:7:17318

Error:  Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.12.1:site (default-site) on project arrow-java-root: failed to get report for org.apache.maven.plugins:maven-javadoc-plugin: Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.5.0:enforce (enforce-maven-version) on project arrow-bom: Execution enforce-maven-version of goal org.apache.maven.plugins:maven-enforcer-plugin:3.5.0:enforce failed: Unable to provision, see the following errors:
Error:  
Error:  1) Error in custom provider, com.google.inject.OutOfScopeException: No MavenProject is executing on this thread.
Error:    at ClassRealm[coreExtension>com.gradle:develocity-maven-extension:1.21.6, parent: ClassRealm[plexus.core, parent: null]] (via modules: org.eclipse.sisu.wire.WireModule -> org.eclipse.sisu.plexus.PlexusBindingModule -> com.gradle.maven.extension.b -> com.gradle.maven.extension.b$a -> com.gradle.maven.cache.extension.h.a)
Error:    while locating com.gradle.maven.cache.extension.d.k
Error: [ERROR] 
Error: [ERROR] 1 error
Error:  -> [Help 1]
Error:  
Error:  To see the full stack trace of the errors, re-run Maven with the -e switch.
Error:  Re-run Maven using the -X switch to enable full debug logging.
Error:  
Error:  For more information about the errors and possible solutions, please read the following articles:
Error:  [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Error:  
Error:  After correcting the problems, you can resume the build with the command
Error:    mvn <args> -rf :arrow-java-root

Can we fix this? Or do we have a workaround for this?

@danepitkin
Copy link
Member

No workaround yet..

It successfully builds Arrow Java with {mvn} clean install, but fails here at {mvn} ... clean install site:

${mvn} -Dcheckstyle.skip=true -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false clean install site

@kou
Copy link
Member

kou commented Aug 13, 2024

Do we know the reason why the failure is happen? Or we need to investigate it as the first step?

@danepitkin
Copy link
Member

We need to investigate. I've tried looking into it with no luck so far. I'm not familiar with these types of error messages.

It seems that the develocity plugin and the javadoc plugin might not be behaving well together. But I can't understand why yet.

@danepitkin
Copy link
Member

I've got it fixed now. Note that there is a new CI failure for this job and that I ran my testing against an older commit on main to verify the Java-related error.

kou pushed a commit that referenced this issue Aug 13, 2024
…adocs (#43674)

### Rationale for this change

Apparently some maven plugins are not thread safe and started throwing errors in the `test-debian-12-docs` CI job when building javadocs.

### What changes are included in this PR?

* Remove multithreading config when building javadocs

### Are these changes tested?

CI

### Are there any user-facing changes?

No
* GitHub Issue: #43378

Authored-by: Dane Pitkin <dpitkin@apache.org>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
@kou kou added this to the 18.0.0 milestone Aug 13, 2024
@kou
Copy link
Member

kou commented Aug 13, 2024

Issue resolved by pull request 43674
#43674

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

No branches or pull requests

4 participants