Repository navigation
Windows arm64 Tests failing on DDARM64-132 #67821
Description
The log does not have any details about the failure.
Console log: 'profiler.rejit' from job 1bec3f43-7d47-4f00-9299-6cefc1cd6299 workitem 365fa792-6588-4765-bb67-642543d541b7 (windows.10.arm64v8.open) executed on machine DDARM64-132
Failed in #67817, #67774 and many other jobs. It is a different test each time. The only common pattern is DDARM64-132 machine name.
Activity
jkotas commentedon Apr 10, 2022
@dotnet/dnceng Could you please remove
DDARM64-132from the pool and check its health?danmoseley commentedon Apr 10, 2022
Cc @dotnet/dncenghot
jakobbotsch commentedon Apr 11, 2022
Similar looking failure in https://dev.azure.com/dnceng/public/_build/results?buildId=1709921&view=ms.vss-test-web.build-test-results-tab&runId=46511082&resultId=108903&paneView=debug on a different machine: https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-67238-merge-9e174ab97ff8449ab2/JIT.HardwareIntrinsics.X86.Avx1/1/console.310ed48e.log?sv=2019-07-07&se=2022-04-30T23%3A51%3A23Z&sr=c&sp=rl&sig=NCIi6AFYy6maoBk1tHEkmJxAq%2FznXMWAbfiHy4IpcIA%3D
dkurepa commentedon Apr 11, 2022
Hello, I'll take the machine offline, you can follow the issue on our side at dotnet/arcade#9016
MattGal commentedon Apr 11, 2022
for -046 (more recent log) I filed dotnet/arcade#9024 (@agocke FYI)
jakobbotsch commentedon Apr 19, 2022
Same problem now seems to be occurring on DDARM64-125, e.g. run 1, run 2.
lpatalas commentedon Apr 19, 2022
I took that machine offline and created dotnet/arcade#9088 to follow up
agocke commentedon Apr 20, 2022
Dup against dotnet/arcade#9088
markwilkie commentedon Apr 20, 2022
I wonder if it makes sense to have a "tracker" known issue to see how often we get hit with machines going offline over time? https://github.com/dotnet/arcade/blob/main/Documentation/Projects/Build%20Analysis/KnownIssues.md
cc/ @ulisesh @AlitzelMendez
ulisesh commentedon Apr 20, 2022
Unfortunately, the output generated by machines in a bad state is empty so we can't generate a known issue for it. I'm not sure how @ilyas1974 is tracking how often machines have to be reimaged