-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Switch to Windows.10.Arm64v8.Open Helix queue #27320
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
Not sure this is going to work but @ilyas1974 was hopeful. See aspnetcore-helix-matrix run https://dev.azure.com/dnceng/public/_build/results?buildId=869710 for actual verification of the change. |
This seems to take aspnetcore-helix-matrix in the right direction but doesn't get us to reliable tests on Windows ARM64. https://dev.azure.com/dnceng/public/_build/results?buildId=869710 shows
Should the above be skipped on the relevant queues❔ Separately whatever happened with https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-aspnetcore-refs-heads-dougbu-alternate13f6996e221a4617ac/Microsoft.AspNetCore.Owin.Tests--net6.0/console.a52732bc.log?sv=2019-07-07 is just strange. https://helix.dot.net/api/jobs/13f6996e-221a-4617-ac28-7bcc4bc4b189/workitems/Microsoft.AspNetCore.Owin.Tests--net6.0?api-version=2019-06-17 doesn't add any information but does show the work item failed. |
https://dev.azure.com/dnceng/public/_build/results?buildId=869784 is new aspnetcore-helix-matrix build to watch |
Rerun now that the SkipHelixArm property was used in halter's pr? |
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
a787416
to
402a18d
Compare
Needed to rebase on master because the other pipeline won't pick up GitHub's merge commit |
Latest aspnetcore-helix-matrix build: https://dev.azure.com/dnceng/public/_build/results?buildId=870503 |
aspnetcore/src/Servers/Kestrel/test/Libuv.FunctionalTests/Libuv.FunctionalTests.csproj Line 11 in a34dc1a
|
This seems just as bad as the other ARM queue. Hangs sometimes on dotnet-install
|
- this may avoid problems with empty `$env:Path` values
- extend `$(CrossgenOutput)` changes to those jobs too
- also make sure internal queues are also skipped in updated attributes
402a18d
to
b271457
Compare
You may be right but the problems still need to be resolved for whenever we get a working Windows ARM64 queue. Trying w/ the correct skips in place this time… |
Last run the only issues in the first attempt were problems downloading Suspect the CDN had a few hiccups… |
Marked ready for review |
@@ -21,7 +21,7 @@ public AppWithDepsTests(ITestOutputHelper logger) | |||
|
|||
[ConditionalFact] | |||
[QuarantinedTest("https://github.com/dotnet/aspnetcore/issues/23994")] | |||
[SkipOnHelix("https://github.com/dotnet/aspnetcore/issues/23360", Queues = "Windows.10.Arm64;Windows.10.Arm64.Open;Debian.9.Arm64;Debian.9.Arm64.Open;(Debian.9.Arm64.Open)Ubuntu.1804.Armarch.Open@mcr.microsoft.com/dotnet-buildtools/prereqs:debian-9-helix-arm64v8-a12566d-20190807161036;(Debian.9.Arm64)Ubuntu.1804.Armarch@mcr.microsoft.com/dotnet-buildtools/prereqs:debian-9-helix-arm64v8-a12566d-20190807161036")] | |||
[SkipOnHelix("https://github.com/dotnet/aspnetcore/issues/23360", Queues = "Windows.10.Arm64;Windows.10.Arm64.Open;Debian.9.Arm64;Debian.9.Arm64.Open;(Debian.9.Arm64.Open)Ubuntu.1804.Armarch.Open@mcr.microsoft.com/dotnet-buildtools/prereqs:debian-9-helix-arm64v8-a12566d-20190807161036;(Debian.9.Arm64)Ubuntu.1804.Armarch@mcr.microsoft.com/dotnet-buildtools/prereqs:debian-9-helix-arm64v8-a12566d-20190807161036;Windows.10.Arm64v8;Windows.10.Arm64v8.Open")] |
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.
related to the trait idea, this would be a case where we could use SkipOnHelix(traits = "arm"), as opposed to listing every arm queue manually :/
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.
Maybe though we don't list all the ARM64 queues that often -- two or three times. Wouldn't recommend adding traits for the small noise reduction. (I also think of traits primarily in the context of command-line filtering e.g. quarantined or not.)
On the other hand, we might want to add a few static public string
s for common queue combinations in the Testing project.
Either way, I'd rather make the larger change separately.
@BrennanConroy @HaoK if comments are resolved from your perspective, please approve 😺 |
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.
You have yet to acknowledge the <SkipHelixArm>true</SkipHelixArm>
comment, or provide a valid reason not to use it.
It would be invalid to use that because the tests do run on Linux ARM64 machines just fine. |
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.
Non-windows ARM, of course!
$env:Path
values