-
Notifications
You must be signed in to change notification settings - Fork 110
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
Incompatible with nightly-2021-09-26: unknown pass name 'sancov' #276
Comments
|
dtolnay
added a commit
to serde-rs/json
that referenced
this issue
Sep 26, 2021
dtolnay
added a commit
to dtolnay/serde-yaml
that referenced
this issue
Sep 26, 2021
There are two straightforward approaches to fixing this but either approach
will also prevent any operation with versions of rustc without newpm. It's
probably fine though?
…On Sun, 26 Sep 2021, 07:13 David Tolnay, ***@***.***> wrote:
- rust-lang/rust#88243 <rust-lang/rust#88243>
looks like the most relevant change.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#276 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFFZUUESHGNBJNDDFQNEDLUD2MXFANCNFSM5EYKN6FQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
ctz
added a commit
to rustls/rustls
that referenced
this issue
Sep 26, 2021
djc
pushed a commit
to rustls/rustls
that referenced
this issue
Sep 26, 2021
Merged
Dirbaio
added a commit
to smoltcp-rs/smoltcp
that referenced
this issue
Sep 26, 2021
rbradford
added a commit
to rbradford/cloud-hypervisor
that referenced
this issue
Sep 27, 2021
This resolves issues between released version of cargo fuzz and nightly. See rust-fuzz/cargo-fuzz#276 Signed-off-by: Rob Bradford <[email protected]>
MrXinWang
pushed a commit
to cloud-hypervisor/cloud-hypervisor
that referenced
this issue
Sep 27, 2021
This resolves issues between released version of cargo fuzz and nightly. See rust-fuzz/cargo-fuzz#276 Signed-off-by: Rob Bradford <[email protected]>
bmc-msft
pushed a commit
to bmc-msft/onefuzz
that referenced
this issue
Sep 27, 2021
bmc-msft
added a commit
to microsoft/onefuzz
that referenced
this issue
Sep 27, 2021
…#1284) See rust-fuzz/cargo-fuzz#276 Co-authored-by: Brian Caswell <[email protected]>
sunfishcode
added a commit
to bytecodealliance/cap-std
that referenced
this issue
Oct 6, 2021
This works around rust-fuzz/cargo-fuzz#276.
sunfishcode
added a commit
to bytecodealliance/cap-std
that referenced
this issue
Oct 7, 2021
) The main tricky part here is that `fs_utf8::DirEntry::file_name()` now has to return `io::Result<String>` instead of just `String` so that it can fail if the name is unencodable. Fixes #186. * Make the `test_invalid_utf8` tolerant of OS's which disallow such paths. It appears MacOS rejects invalid filenames; on such platforms, don't try to test that we can open invalid filenames. * Temporarily disable fuzz test compilation. This works around rust-fuzz/cargo-fuzz#276. * Remove the ubuntu-16.04 builds, as ubuntu-16.04 is no longer supported.
snev68
added a commit
to snev68/cap-std
that referenced
this issue
Aug 5, 2024
…188) The main tricky part here is that `fs_utf8::DirEntry::file_name()` now has to return `io::Result<String>` instead of just `String` so that it can fail if the name is unencodable. Fixes #186. * Make the `test_invalid_utf8` tolerant of OS's which disallow such paths. It appears MacOS rejects invalid filenames; on such platforms, don't try to test that we can open invalid filenames. * Temporarily disable fuzz test compilation. This works around rust-fuzz/cargo-fuzz#276. * Remove the ubuntu-16.04 builds, as ubuntu-16.04 is no longer supported.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I noticed that serde_json's fuzz target does not build using the most recent nightly. It's been working for a long time so this is a recent breakage.
Repro:
The upstream commit range is rust-lang/rust@7342213...addb4da.
The text was updated successfully, but these errors were encountered: