Skip to content

Conversation

@alexcrichton
Copy link
Member

We've got a large crop of fuzz-bugs from fuzzing with
v8-enabled-with-SIMD on CI but at this point the fuzz stats from
oss-fuzz say that the fuzzer is spending less than 50% of its time
actually fuzzing and presumably mostly hitting crashes and such. While
we fix the other issues this disables simd for fuzzing with v8 so we can
try to see if we can weed out other issues.

We've got a large crop of fuzz-bugs from fuzzing with enabled-with-SIMD
on oss-fuzz but at this point the fuzz stats from oss-fuzz say that the
fuzzers like v8 are spending less than 50% of its time actually fuzzing
and presumably mostly hitting crashes and such. While we fix the other
issues this disables simd for fuzzing with v8 so we can try to see if we
can weed out other issues.
@alexcrichton alexcrichton changed the title Temporarily disable SIMD fuzzing with v8 on CI Temporarily disable SIMD fuzzing on CI Sep 20, 2021
@alexcrichton
Copy link
Member Author

I actually went ahead and pushed up a commit that disabled simd for all targets, not just the v8 target.

@github-actions github-actions bot added the fuzzing Issues related to our fuzzing infrastructure label Sep 20, 2021
@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.

@alexcrichton alexcrichton merged commit fc6328a into bytecodealliance:main Sep 20, 2021
@alexcrichton alexcrichton deleted the no-fuzz-simd branch September 20, 2021 19:17
alexcrichton added a commit to alexcrichton/wasmtime that referenced this pull request Sep 22, 2021
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