[
https://issues.apache.org/jira/browse/CALCITE-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748429#comment-17748429
]
Ran Tao edited comment on CALCITE-5878 at 7/28/23 6:12 AM:
-----------------------------------------------------------
hi,devs. I have use [https://github.com/apache/calcite/pull/3340] test many
times, even with a empty commit. The PR check failed in JDK8(windows) and JDK17
(windows).
And i close this PR then create a same content PR
[https://github.com/apache/calcite/pull/3342] then ci check passed. It's maybe
a cached or concurrent error. I think we can add the solution to the
contribution doc. It will be useful.
was (Author: lemonjing):
hi,devs. I have use [https://github.com/apache/calcite/pull/3340] test many
times, even with a empty commit. The PR check failed in JDK8(windows) and JDK11
(windows).
And i close this PR then create a same content PR
[https://github.com/apache/calcite/pull/3342] then ci check passed. It's maybe
a cached or concurrent error. I think we can add the solution to the
contribution doc. It will be useful.
> 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)
