Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Port https://github.com/dotnet/aspnetcore/pull/38814 to 6.0 #40101
Conversation
pranavkm
requested review from
BrennanConroy,
halter73,
Pilchie and
Tratcher
as code owners
|
Hi @pranavkm. If this is not a tell-mode PR, please make sure to follow the instructions laid out in the servicing process document. |
|
The goal is to increase coverage in servicing? Sounds good to me. |
|
@dougbu had attempted to port this back to 6.0 yesterday: #38814 (comment). I'm not super sure of the background on this though. |
We need the following in this PR or the branch is going to get more flaky
https://github.com/dotnet/aspnetcore/blob/main/eng/test-configuration.json#L11
|
|
||
| <!-- https://github.com/dotnet/aspnetcore/issues/38819 LocalDb sometimes hangs on win11 helix queue --> | ||
| <BuildHelixPayload>false</BuildHelixPayload> |
There was a problem hiding this comment.
@dougbu had attempted to port this back to 6.0 yesterday: #38814 (comment). I'm not super sure of the background on this though.
The background is we need this addition in release/6.0 to get PRs passing because LocalDB isn't reliable where we need it to be reliable.
The un-quarantining is also fine as long as the tests have been just as reliable in this branch. If the test or test infrastructure isn't up to the task, we should backport only this change. I'm not familiar enough w/ the tests to know either way and am asking the gathered masses (as I would have if the backport bot could work)…
No description provided.
The text was updated successfully, but these errors were encountered: