Larry Ewing
Larry Ewing
https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-75220-merge-4f48f0e0781f4dfc9a/JIT.jit64/1/console.8abd5707.log?helixlogtype=result
I think we should try setting `DOTNET_CLI_DO_NOT_USE_MSBUILD_SERVER=true` and see what happens here
These all appear to be intermittent runtime tests where msbuild exits with a 1 instead of a 0 and there are also often accompanying restore failures on some tests that...
> Happens also for non-JIT tests: > > * 9/16 AM - Rolling run [20115](https://runfo.azurewebsites.net/view/build/?number=20115) (7.0-rc2) > > * Loader/classloader/generics/Layout/General/Base01b_seq_ser/Base01b_seq_ser.sh > > * error : Failed to resolve SDK 'Microsoft.Build.NoTargets/3.5.0'....
> @lewing did ya'll end up trying disabling msbuild server? If server is potentially the issue here, it'd be good to find that out, get Michal's change into msbuild, get...
have we seen this in main after https://github.com/dotnet/runtime/pull/75743 ?
There have been multiple roslyn/msbuild issues (and some caused by ubuntu's openSSL). I say we take https://github.com/dotnet/runtime/pull/76090 for now and see if things go green. The failures here are definitely...
@jkoritzinsky @trylek can you help walk @rokonec through how the runtime tests build for wasm and why they might trigger interesting failures in the build/compiler servers
if these are all on ubuntu 1804 it may be the openssl issue https://github.com/dotnet/runtime/issues/48411#issuecomment-1178405101 and https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1983100 but I think that had a specific exit code