-
Notifications
You must be signed in to change notification settings - Fork 10.4k
[release/5.0] Update cert that became valid and broke tests #33033
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
Conversation
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
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.
Looks good but failures seem consistent. PR may need something more…
Another one for the @dotnet/aspnet-build team to get in. /fyi @dotnet/aspnet-build https://github.com/dotnet/aspnetcore/pulls/app%2Fgithub-actions shows all PRs the backport bot opened. @Pilchie I marked this one as |
Selenium ChromeDriver version looks to be the issue in release/5.0 for the other failures
|
@HaoK I tried the backport bot w/ @BrennanConroy's #33019 and #33043 PRs. Both need manual work… |
These fixes must go in as part of the first merge for 5.0.8. We should either include 5.0.8 branding in this PR or copy the commits into the 5.0.8 branding PR. |
Closing in favor of #33198 |
* [release/5.9] Update branding to v5.0.8 - disable baseline validation * [release/5.0] Update cert that became valid and broke tests - backport of 2e20bab (#32812) - dupe of #33033 * Update cert to not be valid for 50 years * Make cert valid in 10 years * Delete unused copy of certs, update right one * Skip test for now * [release/5.0] Update Chrome driver - backport of e7b5aa6 (#33019) * [release/5.0] Update selenium chrome driver - backport of af96aba (#33043)
Backport of #32812 to release/5.0
/cc @HaoK
Customer Impact
Testing
Risk