feat(fuzz): prioritize favored corpus entries - #15818
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
|
derek bench fuzz compare-ref=master timeout=600 |
|
cc @mablr bench (fuzz) event published. Results will be reported separately. View publisher run Config: subcommand: |
|
derek bench invariant timeout=10800 |
|
cc @grandizzy bench (invariant) event published. Results will be reported separately. View publisher run Config: subcommand: |
|
derek bench invariant timeout=7200 |
|
cc @mablr bench (invariant) event published. Results will be reported separately. View publisher run Config: subcommand: |
06d1647 to
f667074
Compare
✅ Changelog foundThe deterministic check will validate the changed entry. |
|
derek bench invariant timeout=7200 |
|
cc @mablr bench (invariant) event published. Results will be reported separately. View publisher run Config: subcommand: |
|
derek bench invariant timeout=600 trials=6 paired-seeds=true |
|
cc @mablr bench (invariant) event published. Results will be reported separately. View publisher run Config: subcommand: |
6819746 to
a71075d
Compare
|
derek bench invariant timeout=600 trials=6 paired-seeds=true |
|
cc @grandizzy bench (invariant) event published. Results will be reported separately. View publisher run Config: subcommand: |
a71075d to
af5de41
Compare
af5de41 to
7adb9af
Compare
| .collect() | ||
| } | ||
|
|
||
| fn mutation_energy( |
There was a problem hiding this comment.
maybe worth looking at https://github.com/AFLplusplus/LibAFL/blob/de0b34d2c561256e8d241af1a42851ea8803ab22/crates/libafl/src/schedulers/testcase_score.rs#L53-L267
and the metadata tracking
There was a problem hiding this comment.
Would it make sense to start narrowly with favored status and per-entry selection/productivity counts? These directly inform donor selection using metadata Foundry can already track, while execution-time calibration and full power scheduling would require broader fuzzing-lifecycle changes.
|
This pull request is stale because it has been open for 14 days with no activity. It will be closed in 7 days if there is no further activity. |
|
This pull request was closed because it has been inactive for 7 days since being marked as stale. |
7adb9af to
dea720b
Compare
Refresh the existing scheduling proposal directly on minset culling, without the observed-call or mutator layers. Preserve its weighting policy for review and keep the applicable corpus tests enabled. Co-authored-by: Derek Cofausper <256792747+decofe@users.noreply.github.com>
dea720b to
0e53af4
Compare
|
derek bench invariant |
|
cc @mablr bench (invariant) event published. Results will be reported separately. View publisher run Config: subcommand: |
4 participants
Prioritize mutation donors using the existing favored-entry, edge-rarity, and recent-yield schedule. This refresh places scheduling directly on #15368, without the observed-call dictionary or additional mutation operators. Applicable corpus and synchronization tests remain enabled.
Compare Derek results against the exact #15368 head
e6845bc79to isolate scheduling. The existing expanded weight vector can grow quadratically, the recent-yield bonus retains a floor, and selection remains limited to the in-memory donor pool. Those design questions are deliberately unchanged by this refresh and remain open for review.Originally prompted by @0xalpharush. AI assistance was used for the refresh, conflict resolution, test adaptation, and this description.