Closed
Description
Wasm Microbenchmarks are still failing after the BDN update. Two spots that pop out are a seeming failure with building, although another build of seemingly the same location succeeds after; and an inability to run a specific 'main.js' file from the browser-wasm/AppBundle folder. Respectively:
// start dotnet build -c Release /p:DebugType=portable -bl:benchmarkdotnet.binlog --no-restore /p:UseSharedCompilation=false /p:BuildInParallel=false /m:1 /p:Deterministic=true /p:Optimize=true /p:NuGetPackageRoot="/home/helixbot/work/A50E08AE/p/performance/artifacts/packages" in /home/helixbot/work/A50E08AE/p/performance/artifacts/bin/MicroBenchmarks/Release/net7.0/f55d017a-085a-41d6-a734-6abcdf4c2743
[2022/02/08 12:59:15][INFO] // command took 14.99s and exited with 1
and
[2022/02/08 13:14:47][INFO] // Execute: /home/helixbot/.jsvu/v8 --expose_wasm main.js -- --run f55d017a-085a-41d6-a734-6abcdf4c2743.dll --benchmarkName Burgers.Test2 --job "PowerPlanMode=00000000-0000-0000-0000-000000000000, Runtime=Wasm, Arguments=/p:DebugType=portable,-bl:benchmarkdotnet.binlog, Toolchain=Wasm, IterationTime=250.0000 ms, MaxIterationCount=20, MinIterationCount=15, WarmupCount=1" --benchmarkId 0 in /home/helixbot/work/A50E08AE/p/performance/artifacts/bin/MicroBenchmarks/Release/net7.0/f55d017a-085a-41d6-a734-6abcdf4c2743/bin/net7.0/browser-wasm/AppBundle
[2022/02/08 13:14:47][INFO] Failed to set up high priority. Make sure you have the right permissions. Message: Permission denied
[2022/02/08 13:14:47][INFO] Error reading 'main.js'
[2022/02/08 13:14:47][INFO] No Workload Results were obtained from the run.
Upon further investigation, it looks like the main.js file got renamed to test-main.js. Example ls result in AppBundle:
dotnet.js dotnet.timezones.blat dotnet.wasm icudt.dat index.html managed mono-config.json run-v8.sh supportFiles test-main.js