You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2021/02/15 11:27:31 UTC
[GitHub] [arrow] jorgecarleitao edited a comment on pull request #9493: ARROW-11624: [Rust] Move Arrow benchmarks to its own crate
jorgecarleitao edited a comment on pull request #9493:
URL: https://github.com/apache/arrow/pull/9493#issuecomment-779159015
I am just trying to understand how this reduces the dev cycle: maybe I am not using the correct flow.
My flow atm on the arrow crate is (on a vs terminal opened on `rust/arrow`)
```bash
git checkout master
git checkout -b feature/A
# > remove all workspaces from `../Cargo.toml` since rust-analyzer builds all and I do not care about them.
# > change something
cargo fmt
cargo clippy
cargo test --lib
cargo bench --bench X
# repeat step until happy
# > commit
git checkout master
cargo bench --bench X
git checkout feature/A
cargo bench --bench X
# > copy bench results
```
Open PR with bench results and pray that other dependencies pass. If not, iterate on them.
I am curious as to how others have been working here.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org