Closed kg closed 2 years ago
@naricc
I have reproduced this, but I don't know what is going on yet.
Thanks, let me know if I can help with a binlog or something.
@naricc was this fixed by #1734 or these are two different issues?
This is a different issue.
I am unable to reproduce this issue when following instructions provided by @radical in https://github.com/dotnet/performance/pull/2612
After I updated to the latest dotnet/performance to work on some benchmarks, I got a new and exciting error:
Looking at the bin directory i see x86 and amd64 folders with native DLLs in them (this seems wrong?) and none of the wasm related files, not just dotnet.wasm is missing. It seems like for some reason it generated a native build of the benchmark?
The incantation I'm using to build/run the benchmarks is
dotnet.sh run -f net6.0 -c Release --runtimes Wasm --cli ~/Projects/dotnet-runtime-wasm/dotnet.sh --wasmMainJs ~/Projects/dotnet-runtime-wasm/src/mono/wasm/runtime-test.js --customRuntimePack ~/Projects/dotnet-runtime-wasm/artifacts/bin/microsoft.netcore.app.runtime.browser-wasm/Release --wasmEngine $V8_PATH ${@:2}
in the dotnet/performance repo's latest main rev, 47ed48cf73aeaace0db82d30d9e3f096a2b0b65f, which appears to be using BDN 0.13.0.1559.