[release/5.0] Update dependencies from dotnet/efcore#27189
Conversation
…023.2 Microsoft.EntityFrameworkCore.Tools , dotnet-ef , Microsoft.EntityFrameworkCore , Microsoft.EntityFrameworkCore.Design , Microsoft.EntityFrameworkCore.InMemory , Microsoft.EntityFrameworkCore.Relational , Microsoft.EntityFrameworkCore.Sqlite , Microsoft.EntityFrameworkCore.SqlServer From Version 5.0.0 -> To Version 5.0.0
…023.3 Microsoft.EntityFrameworkCore.Tools , dotnet-ef , Microsoft.EntityFrameworkCore , Microsoft.EntityFrameworkCore.Design , Microsoft.EntityFrameworkCore.InMemory , Microsoft.EntityFrameworkCore.Relational , Microsoft.EntityFrameworkCore.Sqlite , Microsoft.EntityFrameworkCore.SqlServer From Version 5.0.0 -> To Version 5.0.0
|
@dougbu @ajcvickers These seem to be failing pretty consistently with efcore's newest fixes. Can you take a look? |
|
Tagging @pranavkm too. I can't see how this failure is related to an EF update. |
|
That test class references the BasicTestApp project but the containing project uses the Wasm.Authentication.Server. In turn, that project references
@captainsafia @pranavkm is the Wasm.Authentication.Server involved in this particular test❔ |
|
Loads 'o details: |
|
Looking. |
|
This appears to be a flaky test. I can reproduce the failures with some inconsistency, so the right call here would be to quarantine it and go from there. Related, when testing locally, I see our test fixture report issues with Kestrel: @halter73 \ @Tratcher do you know what might cause this? I can't say I've seen this error before today. |
|
@pranavkm that's usually a secondary issue caused by ungraceful shutdown. E.g. It's trying to shut down the host/server while requests are still in flight, probably because of a timeout. From the logs does it look like it's timing out? |
Was it flaky in release/5.0 before getting the latest EF bits❔ If yes, let's get the tests quarantined in this PR. |
|
@dougbu the code path being tested does not use EF at all - it's purely component based code. I'm not worried about the dependency update affecting this test. Trying this out in master, it failed in a similar fashion 1/7 runs. @Tratcher \ @halter73 unfortunately we do not have server logs for these tests (and it's hard to improvise one with the way they're authored). |
I agree with @Tratcher that the most likely cause is ungraceful shutdown. Server logs would make it clear if this is what's happening. Another possibility is that there's something reading/writing request/response data that isn't being properly awaited. |
🆗 then who has the action item to do the quarantining❔ Let's do this quickly… |
|
Updated this PR to include the quarantine. |
This pull request updates the following dependencies
From https://github.com/dotnet/efcore