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

[Flaky test]: Microsoft.AspNetCore.Components.E2ETest.Tests.BootResourceCachingTest.IncrementallyUpdatesCache #20154

Closed
pranavkm opened this issue Mar 25, 2020 · 12 comments
Assignees
Labels
area-blazor Includes: Blazor, Razor Components Done This issue has been fixed feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly task test-failure
Milestone

Comments

@pranavkm
Copy link
Contributor

pranavkm commented Mar 25, 2020

Assert.Collection() Failure
Collection: []
Expected item count: 1
Actual item count:   0


Stack trace
   at Microsoft.AspNetCore.Components.E2ETest.Tests.BootResourceCachingTest.IncrementallyUpdatesCache()
   in /_/src/Components/test/E2ETest/Tests/BootResourceCachingTest.cs:line 92
@pranavkm pranavkm added area-blazor Includes: Blazor, Razor Components feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly labels Mar 25, 2020
@mkArtakMSFT mkArtakMSFT added this to the blazor-wasm-3.2-preview4 milestone Mar 26, 2020
@SteveSandersonMS
Copy link
Member

I don't see anything about this test that implies it should be more flaky than any of the others, so I'm going to unskip it as part of my next PR. If we collect more evidence that there's really a problem specific to this test then of course we need to do more, but we won't get more evidence while it's skipped.

@pranavkm
Copy link
Contributor Author

@SteveSandersonMS I'm not sure what's up with this test. Building it locally works fine both when run in isolation as well as part of dotnet test. I tried a few draft runs with this, but they seemed to pass. Any suggestions on how to proceed with this?

@pranavkm
Copy link
Contributor Author

Dropping this on your plate Steve.

@BrennanConroy BrennanConroy removed this from the 5.0.0 milestone Oct 30, 2020
@mkArtakMSFT mkArtakMSFT added this to the 5.0.0 milestone Oct 30, 2020
@pranavkm pranavkm modified the milestones: 5.0.0, 6.0-preview1 Nov 11, 2020
@SteveSandersonMS
Copy link
Member

Attempting another fix in #29091

@SteveSandersonMS
Copy link
Member

Hopefully fixed in #29091. To make myself check whether this actually worked out in practice, I'm moving this issue forwards to the next milestone.

@SteveSandersonMS
Copy link
Member

Have made yet another attempt to fix this (#30395), so bumping it forwards to preview 3 for verification and possible unquarantining then.

@SteveSandersonMS
Copy link
Member

@mkArtakMSFT Hopefully will be closed with #31154

@SteveSandersonMS
Copy link
Member

Unquarantined in #31154

@ghost ghost added Done This issue has been fixed and removed Working labels Mar 25, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Apr 24, 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 feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly task test-failure
Projects
None yet
Development

No branches or pull requests

5 participants