[
https://issues.apache.org/jira/browse/CALCITE-5785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735518#comment-17735518
]
Akshay Dayal commented on CALCITE-5785:
---------------------------------------
I did a fresh clone and ran:
{quote}./gradlew "-Dorg.gradle.jvmargs=-Xmx1024m -XX:MaxMetaspaceSize=512m"
-Pasf=true -PCI=true --no-build-cache --profile --no-daemon build
{quote}
And got a success. Did this twice.
Is there a docker image or VM used by the build node I can use to try to
reproduce the issue?
https://ge.apache.org/s/v4rrocua72dmg#infrastructure
> The :babel:fmppMain and :server:fmppMain tasks currently do not work with
> Gradle remote build caching
> -----------------------------------------------------------------------------------------------------
>
> Key: CALCITE-5785
> URL: https://issues.apache.org/jira/browse/CALCITE-5785
> Project: Calcite
> Issue Type: Improvement
> Components: build
> Reporter: Akshay Dayal
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.35.0
>
> Attachments: Screenshot 2023-06-17 at 1.21.13 AM.png, Screenshot
> 2023-06-17 at 1.21.28 AM.png
>
>
> The :babel:fmppMain and :server:fmppMain tasks currently do not work with
> remote build caching.
> One of the inputs is a directory and currently it's configured to look at the
> absolute path instead of the relative path. This causes different input
> hashes to be computed on different machines, hence the tasks do not work
> correctly with remote build caching.
> I am attaching screenshots from the build scan analysis showing this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
