[ 
https://issues.apache.org/jira/browse/CALCITE-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748836#comment-17748836
 ] 

Benchao Li commented on CALCITE-5878:
-------------------------------------

I saw two different cases in the log


{code:java}
FAILURE: Build failed with an exception.

* Where:
Settings file 'D:\a\calcite\calcite\settings.gradle.kts' line: 57

* What went wrong:
Could not apply requested plugin [id: 'com.gradle.enterprise', version: 
'3.13.2'] as it does not provide a plugin with id 'com.gradle.enterprise'. This 
is caused by an incorrect plugin implementation. Please contact the plugin 
author(s).
> Plugin with id 'com.gradle.enterprise' not found.

{code}

and 


{code:java}
FAILURE: Build failed with an exception.

* What went wrong:
java.util.concurrent.ExecutionException: org.gradle.api.GradleException: Failed 
to create Jar file 
C:\Users\runneradmin\.gradle\caches\jars-9\81833a0cf63017388de6f4039201d5b5\gradle-enterprise-gradle-plugin-3.13.2.jar.
> org.gradle.api.GradleException: Failed to create Jar file 
> C:\Users\runneradmin\.gradle\caches\jars-9\81833a0cf63017388de6f4039201d5b5\gradle-enterprise-gradle-plugin-3.13.2.jar.

{code}

They seems to be different problem. How often will we run into this? Have you 
tried to reach out to gradle project? If it's known issues, and we can't do 
anything from our side, then I think it will be reasonable to add doc.

> Calcite's ci check process fails due to concurrency errors
> ----------------------------------------------------------
>
>                 Key: CALCITE-5878
>                 URL: https://issues.apache.org/jira/browse/CALCITE-5878
>             Project: Calcite
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 1.35.0
>            Reporter: Ran Tao
>            Priority: Major
>
> I have created a PR from 1.35 calcite main. And the PR failed and cause by:
> [https://github.com/apache/calcite/pull/3340]
> [https://github.com/apache/calcite/actions/runs/5686803178/job/15414233954?pr=3340]
> I have tested with some empty commits, it's failed again. So it's maybe a ci 
> potential bug.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to