Skip to content

Backport #36207 to 6.0 #36247

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 1 commit into from
Sep 8, 2021
Merged

Backport #36207 to 6.0 #36247

merged 1 commit into from
Sep 8, 2021

Conversation

SteveSandersonMS
Copy link
Member

@SteveSandersonMS SteveSandersonMS commented Sep 7, 2021

Having to backport this manually because of #36207 (comment)

Description

Gets the E2E tests into a state where they are ready to rejoin the world of CI. See #36207 for much more detail.

Note that as of this PR, the results are still faked as passed even if they aren't, to ensure nobody is blocked even if something remains incorrect. As described in the original PR, I'll change this to report true results in a week or so when we have enough data.

Customer Impact

Test only

Regression?

  • Yes
  • No

Risk

  • High
  • Medium
  • Low

Test only. Also see the original PR for reasoning on why I think this is likely not to disrupt anyone's work here.

Verification

  • Manual (required)
  • Automated

Packaging changes reviewed?

  • Yes
  • No
  • N/A

…eline (#36207)

* Make E2E tests work on Linux, support retries, and have new Azure pipeline

* Opt components E2E tests out of other CI pipelines (run only in the new one)

* Update src/Components/test/E2ETest/Tests/InputFileTest.cs

Co-authored-by: Martin Costello <[email protected]>

* Move new pipeline logic into old pipeline

Co-authored-by: Your Name <[email protected]>
Co-authored-by: Martin Costello <[email protected]>
@SteveSandersonMS SteveSandersonMS requested review from Pilchie and a team as code owners September 7, 2021 21:13
@SteveSandersonMS SteveSandersonMS added area-blazor Includes: Blazor, Razor Components Servicing-consider Shiproom approval is required for the issue labels Sep 7, 2021
@ghost
Copy link

ghost commented Sep 7, 2021

"Hi SteveSandersonMS. Please make sure you've updated the PR description to use the Shiproom Template. Also, make sure this PR is not marked as a draft and is ready-to-merge.

To learn more about how to prepare a servicing PR click here.

@SteveSandersonMS SteveSandersonMS removed the Servicing-consider Shiproom approval is required for the issue label Sep 8, 2021
@SteveSandersonMS
Copy link
Member Author

As with the other backporting PRs, removing the servicing-consider label since we're not going through shiproom currently for merges to release/6.0.

@dotnet/aspnet-build, can you merge this? Thanks!

@wtgodbe wtgodbe merged commit b934b7f into release/6.0 Sep 8, 2021
@wtgodbe wtgodbe deleted the stevesa/backport-36207-to-6.0 branch September 8, 2021 16:09
@ghost ghost added this to the 6.0-rc2 milestone Sep 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-blazor Includes: Blazor, Razor Components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants