Cargo.toml: allow "fuzzing" as cfg condition name
#6497
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
388d7ea to
caee2f3
Compare
51f90af to
e8ee6b5
Compare
e8ee6b5 to
9e4b474
Compare
|
is it still a draft ? :) |
9e4b474 to
3218b91
Compare
|
GNU testsuite comparison: |
3218b91 to
6eb199c
Compare
in Cargo.toml
6eb199c to
ef68d97
Compare
|
Changes since last push:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR allows "fuzzing" as a
cfgcondition name in order to fix the "unexpectedcfgcondition name:fuzzing" warnings on the nightly builds in the CI (see, for example, https://github.com/uutils/coreutils/actions/runs/9673817439/job/26688539353?pr=6496#step:7:504).