We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rationale
The integration test has a fixed size builder docker image and has builds from several Arrow implementations.
The Rust build artifacts (compiled binaries) in the integration tests still consume ~ 1GB of space even after ARROW-12112: [Rust][CI] Create and store less debug information in CI and integration tests #9879 (see @pitrou's comment on (NOT FOR MERGING) Print out the size of docker container after ARROW-12112 #9884 (comment)).
It would be nice to reduce this even more (and speed up integration test while we are at it)
Reporter: Andrew Lamb / @alamb Assignee: Andrew Lamb / @alamb
Note: This issue was originally created as ARROW-12204. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered:
Andrew Lamb / @alamb: Issue resolved by pull request 9889 #9889
Sorry, something went wrong.
alamb
No branches or pull requests
Rationale
The integration test has a fixed size builder docker image and has builds from several Arrow implementations.
The Rust build artifacts (compiled binaries) in the integration tests still consume ~ 1GB of space even after ARROW-12112: [Rust][CI] Create and store less debug information in CI and integration tests #9879 (see @pitrou's comment on (NOT FOR MERGING) Print out the size of docker container after ARROW-12112 #9884 (comment)).
It would be nice to reduce this even more (and speed up integration test while we are at it)
Reporter: Andrew Lamb / @alamb
Assignee: Andrew Lamb / @alamb
PRs and other links:
Note: This issue was originally created as ARROW-12204. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: