Repository navigation
[wasm] All wasm jobs failing on perf pipeline with .withExitOnUnhandledError is not a function #75268
Description
See log for 20220908.2 on dotnet-runtime-perf pipeline:
[2022/09/08 03:49:16][INFO] Application arguments: --run 8a87bb92-32f6-4903-a08f-b1c480827259.dll --benchmarkName ByteMark.BenchFourier --job PowerPlanMode=00000000-0000-0000-0000-000000000000, Runtime=Wasm, Toolchain=Wasm, IterationTime=250.0000 ms, MaxIterationCount=20, MinIterationCount=15, WarmupCount=1 --benchmarkId 0
[2022/09/08 03:49:16][INFO] test-main.js:262: TypeError: dotnet.withVirtualWorkingDirectory(...).withEnvironmentVariables(...).withDiagnosticTracing(...).withExitOnUnhandledError is not a function
[2022/09/08 03:49:16][INFO] .withExitOnUnhandledError()
[2022/09/08 03:49:16][INFO] ^
[2022/09/08 03:49:16][INFO] TypeError: dotnet.withVirtualWorkingDirectory(...).withEnvironmentVariables(...).withDiagnosticTracing(...).withExitOnUnhandledError is not a function
[2022/09/08 03:49:16][INFO] at run (test-main.js:262:14)
[2022/09/08 03:49:16][INFO]
[2022/09/08 03:49:16][INFO] 1 pending unhandled Promise rejection(s) detected.
This is building c3ccb8a .
Activity
radical commentedon Sep 8, 2022
This is the test-main.js being used.
maraf commentedon Sep 8, 2022
The method is there for the commit you mentioned
runtime/src/mono/wasm/runtime/run-outer.ts
Line 61 in c3ccb8a
pavelsavara commentedon Sep 8, 2022
I think that
dotnet.jsversion used by the test didn't match thetest-main.js.We could check that and fail fast. Draft here #75279
radical commentedon Sep 8, 2022
And I think that happened because the build picked the wrong runtime pack, which is broken on
mainright now.thanks 👍
radical commentedon Sep 10, 2022
Fixed by #75200 . The perf pipeline has a different failure now.