-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Fixed bazel configuration ambiguity for non HTTP3 builds #34483
Fixed bazel configuration ambiguity for non HTTP3 builds #34483
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, thanks @tedjpoole
To avoid ambiguity when building with //bazel:http3=False (on PPC and Windows) this commit adds 2 new config_setting_groups and updates the relevant select() statements. Signed-off-by: Ted Poole <[email protected]>
a10f168
to
d910a0e
Compare
/retest |
Sorry but this fix isn't complete. I have another commit coming in a few minutes... |
My first commit didn't really fix anything. This commit completes the fix. Signed-off-by: Ted Poole <[email protected]>
Signed-off-by: Ted Poole <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, thanks @tedjpoole
@phlax Do you know if the test failures on this are known? They don't look related to the changes |
yeah - it was fixed already i think - ill push this through |
To avoid ambiguity when building with
//bazel:http3=False
(on PPC and Windows) this commit adds 2 newconfig_setting_group
s and updates the relevantselect()
statements.Fixes #34482