Skip to content

Show all targets for which corpora could not be generated #677

@smoelius

Description

@smoelius

Right now, cargo-test-fuzz stops immediately when it cannot generate a corpus for a fuzz target:

ensure!(
corpus_dir.exists(),
"Could not find or auto-generate `{}`. Please ensure `{}` is tested.",
corpus_dir.to_string_lossy(),
target
);

A better approach would be to try to generate a corpus for each fuzz target and, at the end, show the ones for which the operation failed.

I think this should be an easy change.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions