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

[fuzz] Remove more fuzz targets #4737

Merged
merged 2 commits into from
Aug 19, 2022

Conversation

abrown
Copy link
Contributor

@abrown abrown commented Aug 19, 2022

This PR removes the differential fuzz target since its functionality is already covered by the differential_meta target. Then, it renames differential_meta to differential.

@abrown
Copy link
Contributor Author

abrown commented Aug 19, 2022

This PR is dependent on #4735; wait for that one to merge first.

@github-actions github-actions bot added the fuzzing Issues related to our fuzzing infrastructure label Aug 19, 2022
@github-actions
Copy link

Subscribe to Label Action

cc @fitzgen

This issue or pull request has been labeled: "fuzzing"

Thus the following users have been cc'd because of the following labels:

  • fitzgen: fuzzing

To subscribe or unsubscribe from this label, edit the .github/subscribe-to-label.json configuration file.

Learn more.

This functionality is already covered by the `differential_meta` target.
Now that the `differential_meta` fuzz target does everything that the
existing `differential` target did and more, it can take over the
original name.
@abrown abrown marked this pull request as ready for review August 19, 2022 16:55
@alexcrichton alexcrichton enabled auto-merge (squash) August 19, 2022 17:02
@alexcrichton alexcrichton merged commit 9758f54 into bytecodealliance:main Aug 19, 2022
@abrown abrown deleted the remove-more-fuzz-targets branch August 19, 2022 17:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fuzzing Issues related to our fuzzing infrastructure
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants