[
https://issues.apache.org/jira/browse/CALCITE-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748842#comment-17748842
]
Ran Tao commented on CALCITE-5878:
----------------------------------
[~libenchao] hi. benchao.
There are indeed 2 errors here, but I think the root cause is the same. It
should be an occasional concurrency problem (I noticed that the two wrong
checks would fail at the same time). btw, I would like to ask you whether the
window jdk8 and jdk17 check in the same machine? If so, there should be a high
probability that it is a cache problem caused by multiple processes.
I have seen a similar issue [https://github.com/gradle/gradle/issues/20830] in
the gradle community, but it has not been resolved yet. Generally speaking,
local development is not likely to execute two builds at the same time, so it
seems that no developer has reported similar problems. I think we can keep an
eye on this issue. I will also try to see if it can be reproduced locally. WDYT?
> 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)
