sezruby commented on PR #12244: URL: https://github.com/apache/gluten/pull/12244#issuecomment-4653030267
@zhztheplayer @philo-he Pushed a follow-up commit (`a9d80cce3`) that early-returns from `build_arrow_java()` when `uname -m != ppc64le`, so x86_64 / aarch64 contributors skip the redundant local install — gluten-arrow resolves arrow-c-data / arrow-dataset from Maven Central on those archs. ppc64le path is byte-for-byte unchanged. Two CI failures on this run, both unrelated to this PR's diff: - **`spark-test-spark35-slow`** (2m31s) — failed at container init: `Curl error (7): Couldn't connect to server for http://vault.centos.org/centos/8/AppStream/x86_64/os/repodata/repomd.xml`. CentOS 8 mirror outage. - **`spark-test-spark41`** (22m10s) — failed in a `SparkScriptTransformationExec` test asserting `some_non_existent_command` produces a `SparkException`. The error stack is from Spark's subprocess machinery, not gluten code; looks like an environment / flake. Could you re-trigger those two lanes when you get a chance? One caveat worth flagging: every gluten CI lane runs `builddeps-veloxbe.sh` with `BUILD_ARROW=OFF` and uses the pre-built Arrow baked into the Docker image, so the `BUILD_ARROW=ON` path (where `build-arrow.sh` actually executes) is **not covered by CI**. That means the conditional I added isn't exercised by any lane — it relies on a safe-by-construction argument: early-return on non-ppc64le; ppc64le branch byte-for-byte unchanged from before. Worth keeping in mind for review, and probably worth a separate followup to add at least one CI lane that does run `BUILD_ARROW=ON` end-to-end. -- 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]
