Skip to content
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

tests: refresh LE real world verification test case, more logging #71

Merged
merged 2 commits into from
Mar 12, 2024

Conversation

cpu
Copy link
Member

@cpu cpu commented Mar 11, 2024

As described in #68 updating the end-entity certificate used in the Let's Encrypt real world verification integration test suite seems to fix the CI failure in the Android tasks that creeped into main ~2 weeks ago.

There are remaining mysteries to address, but this should be enough to fix CI while we dig deeper.

cpu added 2 commits March 11, 2024 17:09
Previously the `real_world_test` macro only included the test case's
expected result in its log output. This makes it tricky to differentiate
between failures for testcases that share the same expected result (e.g.
`Ok(())`).

This commit updates the macro so the generated test fn includes the
reference subject identifier name as well as the expected result.
* Updates the test cert for presently unknown reasons the previous EE
  cert is returning an error in the Android real world verification test
  suite that appears resolved by refreshing the EE cert.
* Updates the mock verification timestamp to be newer than the LE EE
  cert's NotBefore date.
@cpu cpu self-assigned this Mar 11, 2024
@cpu
Copy link
Member Author

cpu commented Mar 11, 2024

14 successful checks

💚 ✔️

@cpu cpu mentioned this pull request Mar 11, 2024
@complexspaces
Copy link
Collaborator

This seems good to me, but I want to quickly try getting #72 working so we have these logs again first.

@complexspaces complexspaces merged commit 15d487a into rustls:main Mar 12, 2024
14 checks passed
@cpu cpu deleted the cpu-macos-ci-fix branch March 12, 2024 15:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants