Adarsh-Me commented on PR #51315:
URL: https://github.com/apache/arrow/pull/51315#issuecomment-5648177147
CI triage on the failing runs — one real bug (fixed), the rest
infrastructure:
**Fixed at f96c81bcf — the `AMD64 Ubuntu 24.04 R 4.6` / `Windows 2022 Python
3.13` / other from-source pyarrow failures.** Root cause: the
`ARROW_USE_STD_CHRONO` description in `DefineOptions.cmake` used an escaped
backslash (`\\`) before the newline instead of a line-continuation backslash,
so the newline stayed inside the quoted description and leaked into the
generated `ArrowOptions.cmake` as a bare statement line (`AUTO keeps the
current platform default (GH-51267)`). Every consumer that includes the
installed file via `find_package(Arrow)` then failed with `Parse error.
Expected "(", got identifier with text "keeps"` — that's the `ERROR: Failed
building wheel for pyarrow` inside the R docker build and the Windows Python
build. Reproduced locally with the exact generated file, fixed, and verified:
the regenerated `ArrowOptions.cmake` parses clean via `find_package` (`parsed
OK`).
**Not from this PR:**
- `macOS 15-intel C++`, `Windows MinGW CLANG64/MINGW64 C++` (and likely the
remaining MinIO-dependent jobs): `dl.min.io` returns `410: Gone` while
downloading the MinIO release archive — upstream infrastructure.
- `Windows 2022 MATLAB`: workflow template error — `hashFiles('cpp/**,
matlab/**')` failed to hash files on the runner; workflow-side.
- `AMD64 Conda C++ AVX2`: `arrow-filesystem-test` fails with "Attempt to
initialize S3 after it has been finalized" — pre-existing flake, this same job
was the only failure on my merged #51203 as well.
--
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]
