-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Add Win11 helix-matrix/quarantine queue, remove win7/8 #36040
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
Conversation
HaoK
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good assuming the run doesn't crash and burn :)
|
Usually the only thing to watch out for when adding new queues is we have some tests that are skipped on specific queues by name, which will fail whenever we add new ones, but generally those are linux / macOS |
|
Have you run the HTTP/3 & QUIC tests locally recently? I'd expect some failures caused by recent runtime updates that we haven't addressed. I think @JamesNK has a few fixes pending in his PRs. |
dougbu
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't we have some Linux changes e.g. moving to a later version of Debian❔ Suggest we clean up the whole mess at once but it's your call.
Not all of them, but for now they're only running in the quarantine job so that shouldn't be blocking (unless there are unquarantined Quic tests?) |
|
@premun @MattGal getting an error with the new queue:
|
Taking a peek (this is the wrong queue name I'm just fetching it for you) |
|
IIS Cert failures on Win11:
Major Minor Build Revision 10 0 22000 65 CertUtil: -importPFX command completed successfully. SSL Certificate deletion failed, Error: 2 |
|
Also the block I modified apparently doesn't effect quarantine-pr jobs, only the nightly quarantine runs, which is probably fine for getting coverage for now. Test job: https://dev.azure.com/dnceng/public/_build/results?buildId=1338195&view=results |
|
The IIS thing is the same that we saw when the Win10 pool we used got upgraded: https://github.com/dotnet/core-eng/issues/13582#issuecomment-886854042. The solution there was "please revert the upgrade", but I guess here we need to skip all of these tests on Win11 since it is necessarily "too new" - does that sound right @Tratcher? |
|
The issue is in the project setup scripts, you can't even skip the tests, you'd have to skip whole projects. Can you try to repro this locally so we can figure out why the script is failing? Is IIS Express not installed on this agent? |
|
Looking at the script again, it seems to be this line failing?
That would be expected to fail if IIS Express wasn't installed. Also note this isn't exactly the same error as before, before it failed on add, not delete. |
Checking out the definition I see only Windows10Base so unless it were preinstalled on the OS there's definitely no IISExpress here. Checking the original issue (https://github.com/dotnet/core-eng/issues/13582) I don't see that being asked for... feel free to create a dotnet/core-eng issue with your list of requirements and we'll get onto it. |
|
It should be the same requirements as the Win10 machines where we run our IIS tests today, @Tratcher do you remember if we had to get specially configured machines for those? |
|
Right, same requirements as the other windows agents. The only extra thing we'll consider adding later is the Http3Enabled reg key. |
|
Looks like the 20h1 and 21h1 images enable IIS explicitly, but the Windows10-base image doesn't, so we'd want it explicitly enabled for the 11 image as well. I filed https://github.com/dotnet/core-eng/issues/14275 to track that work |
|
IIS and IIS Express are separate. IIS Express is installed by VS, or as a standalone app. |
Understood, please review the artifacts there if you can and let me know if there are any other differences you depend on. |
|
I think that's the only addition we need, I don't believe we need |
|
Update is now rolled out |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
Tests are running now, but we've got some Http3 failures on Win11 (CC @JamesNK @Tratcher)
|
|
@JamesNK @Tratcher @adityamandaleeka any concerns with this PR? If not I can merge, backport, and open issues for the failing tests. |
|
I'm concerned that none of those failures repro locally, but they're all quarantined right? |
|
/backport to release/6.0 |
|
Started backporting to release/6.0: https://github.com/dotnet/aspnetcore/actions/runs/1219112590 |
Part of #36032, #34741