LuciferYang commented on PR #12902: URL: https://github.com/apache/gluten/pull/12902#issuecomment-5434051652
The ClickHouse CI failure here is not from this change's content. That Jenkins job invokes `mvn clean test -Pbackends-clickhouse -Pspark-3.3 -Pjava-8 ... -Dspark.test.home=/tmp/spark33`, and with the `spark-3.3` profile removed it stops at `enforce-spark-profile` with `Missing spark version profile` before anything compiles. So that run says nothing yet about whether the ClickHouse changes in this PR are sound. The command line lives in the job configuration rather than in this repository. I grepped for `ut-stage-1`, `gluten-ci`, and the `-DwildcardSuites=org.apache.gluten` plus `-Dgluten.test.data.path` combination, and there is no in-repo caller; the workspace path and the `io.kyligence:devopslib` parent pom in the warnings both point outside apache/gluten. It needs `-Pspark-3.5` and a Spark 3.5 `spark.test.home`. `backends-clickhouse/pom.xml` declares only a `spark-3.5` profile, so 3.5 is the only target that build can have. One detail for whoever picks this up: the reactor in that log already lists `Gluten Shims for Spark 3.5`, while in this repository `shims/pom.xml` keeps `spark35` inside the `spark-3.5` profile and the only `activeByDefault` profile is `scala-2.12`. That environment therefore looks like it activates `spark-3.5` from its own settings rather than from the command line, which may mean the `-Pspark-3.3` flag and the `/tmp/spark33` path are the only two things that need to change. @jackylee-ch could you help find someone with access to update that job, or point me at where it is configured? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
