Skip to content

Conversation

folkertdev
Copy link
Collaborator

@folkertdev folkertdev commented Sep 4, 2025

cc GitoxideLabs/gitoxide#2148

run with

cargo build --release --examples && poop 'target/release/examples/gix-blame ng' 'target/release/examples/gix-blame rs'

or hyperfine or similar

The data is from running gix blame README.md in the gitoxide repository. These small files disproportionately exercise huffman table parsing/construction.

Copy link

codecov bot commented Sep 4, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.

Flag Coverage Δ
fuzz-compress 40.49% <95.00%> (-0.22%) ⬇️
fuzz-decompress 30.53% <100.00%> (-0.32%) ⬇️
test-aarch64-apple-darwin 92.35% <100.00%> (-0.03%) ⬇️
test-aarch64-unknown-linux-gnu 89.71% <100.00%> (-0.05%) ⬇️
test-i686-unknown-linux-gnu 89.47% <100.00%> (-0.04%) ⬇️
test-x86_64-apple-darwin 90.87% <100.00%> (-0.06%) ⬇️
test-x86_64-unknown-linux-gnu 89.52% <100.00%> (-0.06%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
zlib-rs/src/inflate/inftrees.rs 99.01% <100.00%> (-0.08%) ⬇️

... and 2 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@bjorn3
Copy link
Collaborator

bjorn3 commented Sep 4, 2025

Where did you get these files from?

@folkertdev
Copy link
Collaborator Author

oh, it is from runing gix blame README.md on the gitoxide repo.

@folkertdev
Copy link
Collaborator Author

so basically it's decompressing (parts of?) git commits from that repository

@folkertdev folkertdev force-pushed the gix-blame-example branch 2 times, most recently from df9ac4d to 2375c0e Compare September 17, 2025 13:55
@folkertdev
Copy link
Collaborator Author

Fixed CI on this one and made the input file a lot smaller. I think this is good to go.

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.

2 participants