WasmTestOnNodeJs-System.Threading.Channels.Tests failing with 'RuntimeError: invalid index into function table'

[runfoapp]

Example console.log: https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c8efc49db304496b92/WasmTestOnNodeJs-System.Threading.Channels.Tests/1/console.6ce28db0.log?%3Fsv%3D2019-07-07%26se%3D2022-02-28T10%253A01%253A21Z%26sr%3Dc%26sp%3Drl%26sig%3D6kA2ZDGw6U4aObyqAunyjYSJ%252FvYVemwNYywEToUzifQ%253D

[10:23:15] fail: C:\helix\work\workitem\e\dotnet.js:12
...
[10:23:15] fail: RuntimeError: invalid index into function table
[10:23:15] fail:     at <anonymous>:wasm-function[1884]:0x833dd
[10:23:15] fail:     at <anonymous>:wasm-function[1883]:0x8338e

Runfo Tracking Issue: wasmtestonnodejs-system.threading.channels.tests work item

Build	Definition	Kind	Run Name	Console	Core Dump	Test Results	Run Client
1597924	runtime-extra-platforms	PR 64330	net7.0-Browser-Release-wasm-Mono_Release-WasmTestOnNodeJs-Ubuntu.1804.Amd64.Open	console.log			runclient.py
1596968	runtime-extra-platforms	PR 64330	net7.0-Browser-Release-wasm-Mono_Release-WasmTestOnNodeJs-Ubuntu.1804.Amd64.Open	console.log			runclient.py

Build Result Summary

Day Hit Count	Week Hit Count	Month Hit Count
0	2	2

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Example console.log: https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c8efc49db304496b92/WasmTestOnNodeJs-System.Threading.Channels.Tests/1/console.6ce28db0.log?%3Fsv%3D2019-07-07%26se%3D2022-02-28T10%253A01%253A21Z%26sr%3Dc%26sp%3Drl%26sig%3D6kA2ZDGw6U4aObyqAunyjYSJ%252FvYVemwNYywEToUzifQ%253D

[10:23:15] fail: C:\helix\work\workitem\e\dotnet.js:12
...
[10:23:15] fail: RuntimeError: invalid index into function table
[10:23:15] fail:     at <anonymous>:wasm-function[1884]:0x833dd
[10:23:15] fail:     at <anonymous>:wasm-function[1883]:0x8338e

Runfo Tracking Issue: wasmtestonnodejs-system.threading.channels.tests work item

Build	Definition	Kind	Run Name	Console	Core Dump	Test Results	Run Client
1597924	runtime-extra-platforms	PR 64330	net7.0-Browser-Release-wasm-Mono_Release-WasmTestOnNodeJs-Ubuntu.1804.Amd64.Open	console.log			runclient.py
1596968	runtime-extra-platforms	PR 64330	net7.0-Browser-Release-wasm-Mono_Release-WasmTestOnNodeJs-Ubuntu.1804.Amd64.Open	console.log			runclient.py

Build Result Summary

Day Hit Count	Week Hit Count	Month Hit Count
1	2	2

Author:	runfoapp[bot]
Assignees:	-
Labels:	arch-wasm, untriaged
Milestone:	-

[elinor-fung]

Potentially related to #65012

[radical]

The issue here is different from #65012

                 
[22:51:24] fail: /datadisks/disk1/work/AD3C0936/w/A69B08B4/e/test-main.js:97
                 
[22:51:24] fail: if (typeof globalThis.crypto === 'undefined') {
                 
[22:51:24] fail: ^
                 
[22:51:24] fail: 
                 
[22:51:24] fail: ReferenceError: globalThis is not defined
                 
[22:51:24] fail:     at Object.<anonymous> (/datadisks/disk1/work/AD3C0936/w/A69B08B4/e/test-main.js:97:1)
                 
[22:51:24] fail:     at Module._compile (internal/modules/cjs/loader.js:778:30)
                 
[22:51:24] fail:     at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
                 
[22:51:24] fail:     at Module.load (internal/modules/cjs/loader.js:653:32)
                 
[22:51:24] fail:     at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
                 
[22:51:24] fail:     at Function.Module._load (internal/modules/cjs/loader.js:585:3)
                 
[22:51:24] fail:     at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
                 
[22:51:24] fail:     at startup (internal/bootstrap/node.js:283:19)
                 
[22:51:24] fail:     at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)
          
[22:51:24] info: Process node exited with 1

cc @pavelsavara @maraf

[lewing]

node has defined globalThis since version 12.0.0 so if it is missing it has be set to undefined in that scope

[pavelsavara]

I think we should not try to run on NodeJs lower than 12 and so I wonder how come we do.

[pavelsavara]

Log in the main description is pointing to invalid index into function table but the Runfo links are globalThis is not defined

[pavelsavara]

The globalThis is not defined is issue local to the #64330 and was probably fixed since, right @maraf ?

And runfo is confused here.

[maraf]

The globalThis is not defined is issue local to the #64330 and was probably fixed since, right @maraf?

Yes. Both mentioned builds are those two where I had a bug in extracting node from correlation payload zip and so all node tests failed.

[maraf]

Mentioned builds 1597924 and 1596968 are irrelevant. Main console.log is duplicate of #65012