alamb opened a new pull request, #11212: URL: https://github.com/apache/arrow-rs/pull/11212
# Which issue does this PR close? - Follow on to https://github.com/apache/arrow-rs/pull/10136 # Rationale for this change https://github.com/apache/arrow-rs/pull/10136 added a \`Display runner CPU features\` step to the release test job, intended to show which \`target_feature\`s (e.g. \`bmi2\`) the tests are compiled with. However, \`rustc --print cfg\` does not read the \`RUSTFLAGS\` environment variable, so the step currently prints the *baseline* target features for the target triple rather than the features enabled by \`-C target-cpu=native\`. For example, on my machine: ``` $ rustc --print cfg | grep -c target_feature 28 $ rustc --print cfg -C target-cpu=native | grep -c target_feature 31 ``` # What changes are included in this PR? Pass \`-C target-cpu=native\` explicitly to \`rustc --print cfg\` so the step prints the features that the subsequent \`cargo test --release\` steps are actually built with. # Are these changes tested? By CI (see the output of the \`Display runner CPU features\` step in the \`Test Release Mode\` job). # Are there any user-facing changes? No -- 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]
