Skip to content
New issue

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

[derive] Exclude large test files when publishing #743

Merged
merged 1 commit into from Dec 21, 2023

Conversation

joshlf
Copy link
Member

@joshlf joshlf commented Dec 20, 2023

Exclude the following files from the crate file uploaded to crates.io; they are excessively large, and cause the resulting crate file to be large as well.

  • tests/enum_from_bytes.rs
  • tests/ui-nightly/enum_from_bytes_u16_too_few.rs.disabled

This commit saves a significant amount of space from the published crate file as reported by cargo package:

       Uncompressed   Compressed

Before 3.6MiB 526.8KiB
After 249.9KiB 41.8KiB

This represents a 14x size reduction uncompressed and a 13x size reduction compressed.

Makes progress on #742

Exclude the following files from the crate file uploaded to crates.io;
they are excessively large, and cause the resulting crate file to be
large as well.
- tests/enum_from_bytes.rs
- tests/ui-nightly/enum_from_bytes_u16_too_few.rs.disabled

This commit saves a significant amount of space from the published crate
file as reported by `cargo package`:

           Uncompressed   Compressed
Before     3.6MiB         526.8KiB
After      249.9KiB       41.8KiB

This represents a 14x size reduction uncompressed and a 13x size
reduction compressed.

Makes progress on #742
@joshlf joshlf added this pull request to the merge queue Dec 21, 2023
Merged via the queue into main with commit 330657a Dec 21, 2023
254 checks passed
@joshlf joshlf deleted the exclude-files-from-published-crate branch December 21, 2023 06:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants