Skip to content

Conversation

@alexcrichton
Copy link
Contributor

A historical change last month turned out to break the build of our fuzzers due to new build requirements (wasm blobs built during the fuzzer build), so this adds the corresponding Rust targets to fix the build.

@github-actions
Copy link

github-actions bot commented Jan 5, 2026

alexcrichton is either the primary contact or is in the CCs list of projects/wasmtime.
alexcrichton has previously contributed to projects/wasmtime. The previous PR was #13649

@alexcrichton
Copy link
Contributor Author

The CI failure here is:

cp: error writing '/out/misc': No space left on device

Is this something we should work on on our end to shrink the fuzzers? Or is it ok to expect the failure on github actions knowing that it'll likely pass on the normal oss-fuzz build?

@alexcrichton
Copy link
Contributor Author

Is there anything I can do to help out getting this to merge? Or perhaps this can suffice as a ping? If it's required to that CI is passing I can look to shrink fuzzers, otherwise we'd prefer to get this merged as our fuzzer build has (unknowning to us) been broken for > 1 month

A historical change last month turned out to break the build of our
fuzzers due to new build requirements (wasm blobs built during the
fuzzer build), so this adds the corresponding Rust targets to fix the
build.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant