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

[Blazor] Disable running components E2E tests on Quarantined tests pipeline #37443

Closed
javiercn opened this issue Oct 11, 2021 · 1 comment · Fixed by #37891
Closed

[Blazor] Disable running components E2E tests on Quarantined tests pipeline #37443

javiercn opened this issue Oct 11, 2021 · 1 comment · Fixed by #37891
Assignees
Labels
area-blazor Includes: Blazor, Razor Components Done This issue has been fixed task

Comments

@javiercn
Copy link
Member

These tests now run on their on pipeline aspnetcore-components-e2e, so we should avoid running them elsewhere as the configuration might be different.

@javiercn javiercn added the area-blazor Includes: Blazor, Razor Components label Oct 11, 2021
@mkArtakMSFT mkArtakMSFT added this to the 6.0.0 milestone Oct 12, 2021
@mkArtakMSFT mkArtakMSFT modified the milestones: 6.0.0, 6.0-docs-infra Oct 19, 2021
@TanayParikh
Copy link
Contributor

Confirmed both aspnetcore-quarantined-tests and aspnetcore-quarantined-pr are running the quarantined E2E tests. Both pipelines will need to be updated to stop running those tests.

TanayParikh added a commit that referenced this issue Oct 28, 2021
@ghost ghost added the Working label Oct 28, 2021
@ghost ghost added Done This issue has been fixed and removed Working labels Oct 29, 2021
TanayParikh added a commit that referenced this issue Oct 29, 2021
* Fixes #37443

* CI -> ContinuousIntegrationBuild

* Skip E2EMigration Tests in CI

* Exclude Migration Tests from Helix
@ghost ghost locked as resolved and limited conversation to collaborators Nov 28, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazor Includes: Blazor, Razor Components Done This issue has been fixed task
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants