Ankit Jain

> I am happy to help uploading the new apps but I don't understand how to construct the whole payload for that test. 1. checkout `dotnet/runtime` 2. `make -C src/mono/wasm...

Here's the binlog referenced in the log `Binlog path: /datadisks/disk1/work/AC630921/w/B91B0982/uploads/xharness-output/logs/a2ixs4zc.rtn/build_publish_Release.binlog`: [binlog.zip](https://github.com/dotnet/runtime/files/9418116/binlog.zip)

This is being hit frequently - [two](https://dev.azure.com/dnceng/public/_build/results?buildId=1966436&view=logs&j=6f051c1a-c3e7-5cde-411e-64125624a208&t=961bb5d4-39cc-55d0-23ed-82f28319785b&s=96ac2280-8cb4-5df5-99de-dd2da759617d) new [instances](https://dev.azure.com/dnceng/public/_build/results?buildId=1968277&view=logs&j=6f051c1a-c3e7-5cde-411e-64125624a208&t=961bb5d4-39cc-55d0-23ed-82f28319785b&l=89).

@ilonatommy The `RuntimeList.xml` issue was because WBT on main was broken. Could you please try it again now?

@ilonatommy Also, yours is a different issue. This one is about `dotnet build` exiting with code 1, with *no* errors at all.

And [build](https://dev.azure.com/dnceng-public/public/_build/results?buildId=11388&view=logs&j=e8cc9eb8-98f1-55f3-b6df-6c384ccb39b6&t=d16724ec-b5a0-5bc4-baf7-c436b48cff3d), [log](https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-75200-merge-1dc6991bb94a4f2dab/JIT.Regression/1/console.d5a5987a.log?helixlogtype=result): ``` JIT/Regression/JitBlue/Runtime_74126/Runtime_74126/Runtime_74126.sh [FAIL] Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object at Runtime_74126.GetVtor[Vector256`1](Vector256`1 vtor) at Runtime_74126.Main() [ERROR] FATAL UNHANDLED EXCEPTION: System.NullReferenceException: Object...

@ilonatommy just curious, is VS using the `privateProperties` part?

Also, it would be a good idea to remove all the `__*` fields that we add to the json for our consumption, before sending them out from the proxy. The...

> happening on main, moving to 8.0.0. @naricc @radical - how deterministic is this error, why haven't we seen it on other runs ? No idea. I saw this on...

Closing this as there is only one issue left - https://github.com/dotnet/runtime/issues/89482 , and marking that for 8.0 .