-
Notifications
You must be signed in to change notification settings - Fork 753
test(integration): add BoringSSL cohort to expand mTLS coverage #5659
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
Merged
Merged
Changes from 25 commits
Commits
Show all changes
26 commits
Select commit
Hold shift + click to select a range
6341199
Add feature gated boringssl harness
kaukabrizvi 57a190a
Add boringssl harness
kaukabrizvi fad110f
Type changes since rebase
kaukabrizvi feeff69
Add mtls tests cases for boringssl
kaukabrizvi b34de83
Remove unused imports
kaukabrizvi 49ae2a1
cleanup PR
kaukabrizvi 8eac659
additional cleanup
kaukabrizvi dd658cc
Add comment for cargo config
kaukabrizvi d6a7e49
Apply formatting rules
kaukabrizvi bee0027
clippy fix and macOS CI debug
kaukabrizvi b17e48c
install binutils in macOS runner
kaukabrizvi 59895bc
set objocpy env var for macOS build
kaukabrizvi 5636273
try LLVM instead of bin utils
kaukabrizvi 96ce5cf
Add go to nix packages
kaukabrizvi c8e52ca
Add protocol versions to boring mTLS tests
kaukabrizvi 689b5b0
Apply cargo format
kaukabrizvi 429db60
Debug message to print macOS symbols
kaukabrizvi a082354
Feature gate boringssl to not build on macOS
kaukabrizvi 24aff57
Apply cargo fmt
kaukabrizvi df0ed60
adjust cargo.toml for OS gating
kaukabrizvi 638d454
Add comments to explain broginssl gating
kaukabrizvi 24cce5f
Apply cargo fmt
kaukabrizvi cc22199
More closely match openssl harness
kaukabrizvi 5f5cf65
Feature gate boringssl
kaukabrizvi 8760ec8
Merge branch 'main' into add-boringssl-harness
kaukabrizvi 3c78451
Point to fork's main branch
kaukabrizvi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
I'm fine with this, but can we just open an issue to find a way to "time bomb" ourselves? I'd like our CI to fail if your fork goes more than e.g. 6 months without a commit. "trust but verify" 😉
Uh oh!
There was an error while loading. Please reload this page.
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.
I’ve installed https://wei.github.io/pull/ on the fork, which should help keep it in check. That said, an additional guardrail would be useful - I’ll open a follow-up issue after this lands to add a CI “time-bomb” so the fork doesn’t silently go stale.