Repository navigation
Closed
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tabarea-Infrastructure-monoblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
Description
Build Information
Build error leg:
- linux_bionic-arm64 Release AllSubsets_Mono
Tests failing:
- Microsoft.Bcl.AsyncInterfaces.Tests.WorkItemExecution
- Microsoft.Extensions.DependencyInjection.ExternalContainers.Tests.WorkItemExecution
- System.Diagnostics.DiagnosticSource.Switches.Tests.WorkItemExecution
- System.IO.Pipes.Tests.WorkItemExecution
- System.Linq.Queryable.Tests.WorkItemExecution
Pull request: #86652
Error Message
Fill the error message using step by step known issues guidance.
{
"ErrorMessage": "crit: Failed to find compatible device: arm64-v8a",
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 0 | 8 | 64 |
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=323893
Error message validated: crit: Failed to find compatible device: arm64-v8a
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 6/28/2023 9:22:27 PM UTC
Metadata
Metadata
Assignees
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tabarea-Infrastructure-monoblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
Activity
[-][mono] Tests failing on `linux_bionic-arm64 Release AllSubsets_Mono` with corerun.exe not found[/-][+][mono] Tests failing with corerun.exe not found[/+][-][mono] Tests failing with corerun.exe not found[/-][+]Tests failing with corerun.exe not found[/+]jakobbotsch commentedon Jun 8, 2023
@ivanpovazan I think this log statement is from
runtime/src/tests/Common/helixpublishwitharcade.proj
Line 702 in 03f2be6
and is harmless. E.g. it triggered on my #87165 for the JIT.opt workitem but the actual failure there was #87258
ivanpovazan commentedon Jun 8, 2023
@jakobbotsch thanks for the info!
Does it mean that the issue goes away on retries?
jakobbotsch commentedon Jun 8, 2023
I don't think there is an issue related to that log statement and I don't think it causes the work items to fail. So you should look for other failures in the logs. E.g. in
https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-86652-merge-1c9c9cfd4ebd4ec7b3/System.IO.Pipes.Tests/1/console.5b1e5bba.log?helixlogtype=result
(for the System.IO.Pipelines failure in net8.0-linux-Release-arm64-Mono_Release_LinuxBionic-Windows.10.Amd64.Android.Open), the log ends with "ERROR: The process "corerun.exe" not found.", but the actual failure is above that:
So for example you could use
System.IO.Pipes.Tests.NamedPipeTest_CreateServer.PipeOptions_FirstPipeInstanceWithSameNameReuse_Throws_UnauthorizedAccessException [FAIL]as the error message in the known error template. Using "ERROR: The process "corerun.exe" not found",` is causing tons of unrelated PRs to be linked to this issue.[-]Tests failing with corerun.exe not found[/-][+][mono] Tests failing with `Failed to find compatible device: arm64-v8a`[/+]ivanpovazan commentedon Jun 8, 2023
Thank you very much for the detailed explanation, and sorry for the confusion.
I have updated the search term to be:
crit: Failed to find compatible device: arm64-v8ainstead of wrongly accusedcorerun.exe not foundThis issue seems to be related to a missing device on
linux_bionic-arm64 Release AllSubsets_Mono, while on thelinux_bionic-x64 Release AllSubsets_Mono(note the difference in architecture) there is the failing test @jakobbotsch noted above:I will create a separate tracking issue as these don't seem to be related.
akoeplinger commentedon Nov 24, 2023
The recent failures were because of a broken machine: DNCENGWIN-038
It was fixed recently (dotnet/dnceng#1383 (comment)) so closing this.