-
Notifications
You must be signed in to change notification settings - Fork 10.3k
[release/3.1] Update cert then rebrand #33034
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
@@ -179,7 +179,8 @@ public async Task VerifyExpiredSelfSignedPassesIfDateRangeValidationIsDisabled() | |||
Assert.Equal(HttpStatusCode.OK, response.StatusCode); | |||
} | |||
|
|||
[Fact] | |||
[ConditionalFact] | |||
[SkipOnHelix("https://github.com/dotnet/aspnetcore/issues/32813")] |
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.
Test ran in CI build. Why❔
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.
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.
More proof that we weren't only running things on helix yet... SkipOnHelix has no effect on azdo jobs. The results file name is not the helix queue form either
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.
Skipping on linux since for some reason this test is failing only on ubuntu with the new cert
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.
WFM if you can get CI build working
Things are green now @dougbu not sure if I'm supposed to do anything else from here to get this in, but this should address the test failures in release/3.1 |
Nothing more to do 'til the release/3.1 branch is branded for 3.1.17. @dotnet/aspnet-build will get this in at the right time. |
(We may need to do branding in this PR to avoid CI failures in that work.) |
/fyi @Pilchie I marked this as |
FYI @dotnet/aspnet-build I'm doing branding in this PR |
/fyi I renamed the PR to cover what's going on |
Backport of #32812 to release/3.1
/cc @HaoK
Customer Impact
Testing
Risk