Skip to content

Fuzz clean logs#4497

Draft
joostjager wants to merge 3 commits intolightningdevkit:mainfrom
joostjager:fuzz-clean-logs
Draft

Fuzz clean logs#4497
joostjager wants to merge 3 commits intolightningdevkit:mainfrom
joostjager:fuzz-clean-logs

Conversation

@joostjager
Copy link
Contributor

No description provided.

@ldk-reviews-bot
Copy link

👋 Hi! I see this is a draft PR.
I'll wait to assign reviewers until you mark it as ready for review.
Just convert it out of draft status when you're ready for review!

@joostjager joostjager force-pushed the fuzz-clean-logs branch 2 times, most recently from e88eb4c to b2ea4c4 Compare March 19, 2026 15:08
@codecov
Copy link

codecov bot commented Mar 19, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.18%. Comparing base (7d82e14) to head (e5aa5df).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4497      +/-   ##
==========================================
- Coverage   86.19%   86.18%   -0.02%     
==========================================
  Files         161      160       -1     
  Lines      107459   107441      -18     
  Branches   107459   107441      -18     
==========================================
- Hits        92621    92594      -27     
- Misses      12219    12227       +8     
- Partials     2619     2620       +1     
Flag Coverage Δ
tests 86.18% <ø> (-0.02%) ⬇️

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

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

The sanity check (cargo test on fuzz targets) doesn't use the
restored corpus and was blocking the actual fuzz run. Move it to
a separate fuzz_sanity job so both run in parallel.

AI tools were used in preparing this commit.
Replace the fixed 30s run_time with iteration counts scaled to 8x
corpus size (plus a 1000 baseline) with a 10-minute hard cap. This
ensures small targets finish quickly while large ones get adequate
fuzzing time.

Additional changes:
- Use -q (quiet) to suppress per-iteration status output
- Log corpus size before/after fuzzing with delta
- Increase per-input timeout to 3s for chanmon_consistency_target
- On main, run corpus minimization after each target and report
  the minimized corpus size

AI tools were used in preparing this commit.
@joostjager joostjager force-pushed the fuzz-clean-logs branch 2 times, most recently from 99b19be to bf29ed2 Compare March 20, 2026 08:09
Add timestamp logging to each phase for profiling. Print a summary
table at the end with per-target iterations, corpus sizes, fuzz
run time, and minimization stats. Temporarily run minimization on
all branches for testing.

AI tools were used in preparing this commit.
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