Skip to content

Bump BoringSSL and/or OpenSSL in CI#10391

Merged
alex merged 1 commit intomainfrom
create-pull-request/patch
Feb 15, 2024
Merged

Bump BoringSSL and/or OpenSSL in CI#10391
alex merged 1 commit intomainfrom
create-pull-request/patch

Conversation

@pyca-boringbot
Copy link
Contributor

@pyca-boringbot pyca-boringbot bot commented Feb 14, 2024

BoringSSL

Commit: ba5eb621d7d9bf2872386b4303fd5e9aa64f7230

Diff between the last commit hash merged to this repository and the new commit.

OpenSSL

Commit: d597b46f9bdb533761e36fcf1d96ce83f3f6f04d

Diff between the last commit hash merged to this repository and the new commit.

alex
alex previously approved these changes Feb 14, 2024
@alex alex enabled auto-merge (squash) February 14, 2024 00:29
@alex
Copy link
Member

alex commented Feb 14, 2024

@mhils any idea what's going on with the mitmproxy tests?

@mhils
Copy link
Member

mhils commented Feb 14, 2024

@alex: thanks for the heads-up. This is likely caused by mitmproxy/mitmproxy@2a82674 - I'll make the tests OpenSSL version-agnostic tonight. :)

@alex
Copy link
Member

alex commented Feb 14, 2024 via email

@pyca-boringbot pyca-boringbot bot force-pushed the create-pull-request/patch branch from 0e5e27d to b913cbc Compare February 15, 2024 00:08
mhils added a commit to mitmproxy/mitmproxy that referenced this pull request Feb 15, 2024
This re-adds some log messages adjusted in
2a82674. We shouldn't fail tests for
this.

refs pyca/cryptography#10391
@alex alex merged commit d60e8b6 into main Feb 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants