Lstarsky0 opened a new issue, #10750: URL: https://github.com/apache/arrow-rs/issues/10750
`.github/workflows/integration.yml` filters on 17 `arrow-*` paths, but the two jobs it runs compile 20 crates between them, and the sets don't line up in either direction. The Rust side builds exactly one package — apache/arrow's `ci/scripts/rust_build.sh` runs `cargo build -p arrow-integration-testing` — and the pyarrow job builds `arrow-pyarrow-integration-testing`. Between them they pull in `arrow-arith`, `arrow-cmp`, `arrow-flight` and `arrow-row`, and none of those are in the filter, so a PR touching only one of them never starts the workflow. `arrow-flight` is the surprising one: it's a direct dependency of `arrow-integration-testing`. The other direction: `arrow-avro/**` is in the filter but nothing in either job reaches it. It went in with #4888, the commit that created the crate, and even at that commit `arrow-integration-testing` didn't depend on it. arrow-avro has had 25 commits in the last three months, each paying for a workflow that checks out six other implementations and can't be affected by the change. Both sets are derivable: ``` cargo tree -p arrow-integration-testing --edges normal --prefix none | grep -oE "^arrow[a-z-]*" cd arrow-pyarrow-integration-testing && cargo tree --edges normal --prefix none | grep -oE "^arrow[a-z-]*" ``` Came out of @Rich-T-kid's question on #10724. -- 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]
