Rust: cargo fuzz command not found (missing in docker image?) #12168
Comments
I don't think pinning the action version will help in this case (but I'm not very familiar with this repo, so would be happily corrected!). I suspect the issue might be related to the |
|
I'm getting same build error with following rust projects, It might be a wider issue affecting many rust projects:
|
Mingun
changed the title
|
cargo install at: is failing with following error: Tested with following command: BUILDKIT_PROGRESS=plain docker build --no-cache -t gcr.io/oss-fuzz-base/base-builder-rust --file $PWD/infra/base-images/base-builder-rust/Dockerfile $PWD/infra/base-images/base-builder-rust |
|
That feeling when you follow the repository, you see this PR and the problems that it has already created in a couple of projects, but you do not associate it with your problems 😕 . The issue: serde-rs/serde#2767 |
|
So it seems that changing this line to nightly-2024-07-07 should fix the issue: |
Only changing this line will likely break the coverage build. (The changes from https://github.com/google/oss-fuzz/pull/12077/files would be needed as well) Would it be possible to use a previous version of serde instead? |
|
I believe the easiest fix for this would be to add |
I was just typing this :) Edit: |
Helps pin dependencies at the time of when `cargo-fuzz` itself was published to avoid dependency updates breaking builds. This fixes a current issue where all Rust projects using `cargo fuzz` are broken due to the installation of `cargo-fuzz` failing due to failing to build a newer dependency with an older nightly. Closes google#12168
This is because serde does not build on older nightly cf serde-rs/serde#2770 (comment) and #12171 for a workaround |
I thought so, Thanks for the workaround. |
Helps pin dependencies at the time of when `cargo-fuzz` itself was published to avoid dependency updates breaking builds. This fixes a current issue where all Rust projects using `cargo fuzz` are broken due to the installation of `cargo-fuzz` failing due to failing to build a newer dependency with an older nightly. Closes #12168
It was recently fixed, see google/oss-fuzz#12168 (comment) for details.
|
Hi! OpenSK still fails when running with the same error as above. Probably related to us pinning the compiler version here? #12013 |
|
@kaczmarczyck Looks like the failure is when compiling serde, so maybe temporarily pinning serde, like 037a2b0 may fix it? |
Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=70211#c2 Related issue google#12168 Fix inspired by google@037a2b0
|
Thanks! It works locally, so let's try #12269 |
Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=70211#c2 Related issue #12168 Fix inspired by 037a2b0
It was recently fixed, see google/oss-fuzz#12168 (comment) for details.
Hi! I'm maintainer of quick-xml. Recently I noticed, that build fuzzers for project is unsuccessful, last logs is here:
The reason is that
cargo fuzzcommand was not found (in docker image?).The end of GitHub Action run (too long for issue to post full log)
There was no changes quick-xml side in fuzzing settings. Why build failed? I noticed that steps refers to the
masterbranch of required actions, it that correct? Maybe some breaking changes was made in action and I should use some tag instead? But official example still offers usingmaster...The text was updated successfully, but these errors were encountered: