Matous Kozak

/azp run runtime-extra-platforms

/azp run runtime-extra-platforms

The first rolling-build failure can be tracked down to is https://dev.azure.com/dnceng-public/public/_build/results?buildId=645838&view=results https://github.com/dotnet/runtime/commit/92b9dcaa9cf15d5ca207d5d491cd5e476ff5d6c3. The range between first failure and last known green build is https://github.com/dotnet/runtime/compare/1a820cbf867abfa68acc5d7fb9c925a47132f36f...92b9dcaa9cf15d5ca207d5d491cd5e476ff5d6c3. However, I don't see any interpreter...

> removing blocking-clean-ci as it has not failed in 30 days > > 24-Hour Hit Count 7-Day Hit Count 1-Month Count > 0 0 0 Per our offline discussion, the...

@SamMonoRT The test is enabled on current main and is not failing (e.g. here under Regression_4 test group https://dev.azure.com/dnceng-public/public/_build/results?buildId=502560&view=logs&j=865b3f99-ad28-593e-9358-70d899cc4be9). ``` 20:59:31.278 Running test: JIT/Regression/VS-ia64-JIT/M00/b113493/b113493/b113493.cmd Return code: 0 Raw output file:...

Removing the `Xamarin.Hosting: Failed to connect to port` match string because it's too general and it's matching un-related failures. I'll keep the issue fyi: @ivanpovazan @kotlarmilos

> @vitek-karas this appears to be a linker hang, it is difficult to see in action because AZDO clears the data when it cancels the task This is the last...

> We're going to try #97491 to work around this @lewing looks like https://github.com/dotnet/runtime/pull/97491 fixed the EAT lines, but the linux LibraryTests_AOT line is still crashing (https://dev.azure.com/dnceng-public/public/_build/results?buildId=546947&view=logs&j=58dc7ccb-0414-5dd3-62a5-bf2e63258b7c&t=4105ec49-25d1-5748-9e28-e40bff74a16b)

The error message (`ninja: build stopped: subcommand failed.`) is too general and it is matching unrelated failures such as ``` C:\PROGRA~1\MICROS~1\2022\Preview\VC\Tools\MSVC\1439~1.333\bin\Hostx86\arm64\cl.exe /nologo -DHAVE_CONFIG_H -DLLVM_API_VERSION=1600 -DNO_GLOBALIZATION_SHIM -ID:\a\_work\1\s\artifacts\obj -ID:\a\_work\1\s\src\native -ID:\a\_work\1\s\artifacts\obj\mono\android.arm64.Release\cross\mono\mini -ID:\a\_work\1\s\artifacts\obj\mono\android.arm64.Release\cross\mono\mini\..\.. -ID:\a\_work\1\s\src\mono\mono\mini\..\.....

> Well, setting `ArtifactsPath` seems to work for every runtime except wasm (and probably MonoAOTLLVM, but we don't have any tests for it). Might you have any insight on that...