swift-nio: fix broken build #14719
Open
swift-nio: fix broken build #14719
Conversation
This file contains hidden or 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
|
xingyaner is a new contributor to projects/swift-nio. The PR must be approved by known contributors before it can be merged. The past contributors are: catenacyber, asraa |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The fuzzing build error occurs because the latest source code of the project has been updated to require the Swift 6.0 toolchain, while the OSS-Fuzz base image currently only provides Swift 5.10.1, resulting in a version mismatch error.
By modifying the Dockerfile, a specific older version code compatible with Swift 5.10 (Tag 2.55.0) was forcibly checked out, thus avoiding toolchain conflicts caused by upstream dependency upgrades and enabling the build to be successful.