You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Francois Saint-Jacques (Jira)" <ji...@apache.org> on 2020/04/30 18:56:00 UTC

[jira] [Assigned] (ARROW-8648) [Rust] Optimize Rust CI Build Times

     [ https://issues.apache.org/jira/browse/ARROW-8648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Francois Saint-Jacques reassigned ARROW-8648:
---------------------------------------------

    Assignee: Mark Hildreth

> [Rust] Optimize Rust CI Build Times
> -----------------------------------
>
>                 Key: ARROW-8648
>                 URL: https://issues.apache.org/jira/browse/ARROW-8648
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Rust
>            Reporter: Mark Hildreth
>            Assignee: Mark Hildreth
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> In the Rust CI workflows (rust_build.sh, rust_test.sh), there are some build options used that are at odds with each other, resulting in multiple redundant builds where a smaller number could do the same job. The following tweaks, at minimal, could reduce this, speeding up build times:
>  * Ensure that RUSTFLAGS="-D warnings" is used for all cargo commands. Currently, it's only used for a single command (the {{build --all-targets}} in {{rust_build.sh}}). Subsuquent runs of cargo will ignore this first build, since RUSTFLAGS has changed.
>  * Don't run examples in release mode, as that would force a new (and slower) rebuild, when the examples have already been built in debug mode.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)