Merged
Conversation
Signed-off-by: JP Simard <jp@jpsim.com>
keith
approved these changes
Apr 22, 2022
Contributor
Author
|
Verified with a few common build+test targets: The only thing I know to be broken is Something else may be broken, but I haven't seen it. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Now that we've pulled in envoyproxy/envoy#20852, I'm no longer seeing linker errors when running Swift tests for iOS as reported in #2101.
Risk Level: Low to the libraries, Moderate to local development on an M1 Mac.
Testing:
./bazelw test //test/swift:test --config=iospassesDocs Changes: N/A
Release Notes: N/A