Closed ivanpovazan closed 9 months ago
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries See info in area-owners.md if you want to be subscribed.
Author: | ivanpovazan |
---|---|
Assignees: | - |
Labels: | `area-Infrastructure-libraries`, `blocking-clean-ci`, `Known Build Error` |
Milestone: | - |
@ivanpovazan I think this log statement is from https://github.com/dotnet/runtime/blob/03f2be66ea268a1ea285899f56f55b81e5a25044/src/tests/Common/helixpublishwitharcade.proj#L702 and is harmless. E.g. it triggered on my #87165 for the JIT.opt workitem but the actual failure there was #87258
@jakobbotsch thanks for the info! Does it mean that the issue goes away on retries?
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:
[02:00:43] info: An error occurred running System.IO.Pipes.Tests.sh
[02:00:43] dbug: Exit code: 1
Std out:
Discovering: System.IO.Pipes.Tests (method display = ClassAndMethod, method display options = None)
Discovered: System.IO.Pipes.Tests (found 107 of 538 test cases)
Starting: System.IO.Pipes.Tests (parallel test collections = on, max threads = 8)
System.UnauthorizedAccessException : Access to the path '/data/local/tmp/CoreFxPipe_g2n3xo52.px0' is denied.
Stack Trace:
/_/src/libraries/System.IO.Pipes/src/System/IO/Pipes/NamedPipeServerStream.Unix.cs(336,0): at System.IO.Pipes.NamedPipeServerStream.SharedServer..ctor(String path, Int32 maxCount, Boolean isFirstPipeInstance)
/_/src/libraries/System.IO.Pipes/src/System/IO/Pipes/NamedPipeServerStream.Unix.cs(279,0): at System.IO.Pipes.NamedPipeServerStream.SharedServer.Get(String path, Int32 maxCount, PipeOptions pipeOptions)
/_/src/libraries/System.IO.Pipes/src/System/IO/Pipes/NamedPipeServerStream.Unix.cs(43,0): at System.IO.Pipes.NamedPipeServerStream.Create(String pipeName, PipeDirection direction, Int32 maxNumberOfServerInstances, PipeTransmissionMode transmissionMode, PipeOptions options, Int32 inBufferSize, Int32 outBufferSize, HandleInheritability inheritability)
/_/src/libraries/System.IO.Pipes/src/System/IO/Pipes/NamedPipeServerStream.cs(82,0): at System.IO.Pipes.NamedPipeServerStream..ctor(String pipeName, PipeDirection direction, Int32 maxNumberOfServerInstances, PipeTransmissionMode transmissionMode, PipeOptions options, Int32 inBufferSize, Int32 outBufferSize, HandleInheritability inheritability)
/_/src/libraries/System.IO.Pipes/src/System/IO/Pipes/NamedPipeServerStream.cs(39,0): at System.IO.Pipes.NamedPipeServerStream..ctor(String pipeName, PipeDirection direction, Int32 maxNumberOfServerInstances, PipeTransmissionMode transmissionMode, PipeOptions options)
/_/src/libraries/System.IO.Pipes/tests/NamedPipeTests/NamedPipeTest.CreateServer.cs(263,0): at System.IO.Pipes.Tests.NamedPipeTest_CreateServer.PipeOptions_FirstPipeInstanceWithSameNameReuse_Throws_UnauthorizedAccessException()
/_/src/mono/System.Private.CoreLib/src/System/Reflection/MethodInvoker.Mono.cs(30,0): at System.Reflection.MethodInvoker.InterpretedInvoke(Object obj, IntPtr* args)
/_/src/libraries/System.Private.CoreLib/src/System/Reflection/MethodInvoker.cs(59,0): at System.Reflection.MethodInvoker.Invoke(Object obj, IntPtr* args, BindingFlags invokeAttr)
Finished: System.IO.Pipes.Tests
=== TEST EXECUTION SUMMARY ===
System.IO.Pipes.Tests Total: 150, Errors: 0, Failed: 1, Skipped: 0, Time: 2.364s
Std err:
System.IO.Pipes.Tests.NamedPipeTest_CreateServer.PipeOptions_FirstPipeInstanceWithSameNameReuse_Throws_UnauthorizedAccessException [FAIL]
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.
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-v8a
instead of wrongly accused corerun.exe not found
This issue seems to be related to a missing device on linux_bionic-arm64 Release AllSubsets_Mono
, while on the linux_bionic-x64 Release AllSubsets_Mono
(note the difference in architecture) there is the failing test @jakobbotsch noted above:
System.IO.Pipes.Tests.NamedPipeTest_CreateServer.PipeOptions_FirstPipeInstanceWithSameNameReuse_Throws_UnauthorizedAccessException [FAIL]
I will create a separate tracking issue as these don't seem to be related.
Tagging subscribers to this area: @directhex See info in area-owners.md if you want to be subscribed.
Author: | ivanpovazan |
---|---|
Assignees: | - |
Labels: | `blocking-clean-ci`, `untriaged`, `area-Infrastructure-mono`, `Known Build Error` |
Milestone: | - |
The recent failures were because of a broken machine: DNCENGWIN-038 It was fixed recently (https://github.com/dotnet/dnceng/issues/1383#issuecomment-1819935281) so closing this.
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=298055
Build error leg:
Tests failing:
Pull request: https://github.com/dotnet/runtime/pull/86652
Error Message
Fill the error message using step by step known issues guidance.
Report
Summary
Known issue validation
Build: :mag_right: https://dev.azure.com/dnceng-public/public/_build/results?buildId=323893 Error message validated:
crit: Failed to find compatible device: arm64-v8a
Result validation: :white_check_mark: Known issue matched with the provided build. Validation performed at: 6/28/2023 9:22:27 PM UTC