search

dotnet / runtime

.NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
https://docs.microsoft.com/dotnet/core/
MIT License
14.61k stars 4.56k forks source link

[wasm] JavaScriptCore tests are failing on Windows #49884

Open radekdoulik opened 3 years ago

radekdoulik commented 3 years ago

The library tests are failing on Windows with JavaScriptCore. We are ignoring it for now, this issue is a reminder to look into it later.

    XHarness command issued: wasm test --app=. --engine=javascriptcore --js-file=runtime.js --output-directory=C:\Users\rodo\git\runtime\artifacts\bin\System.Coll
  ections.Concurrent.Tests\net6.0-Debug\browser-wasm\AppBundle\xharness-output -- --run WasmTestRunner.dll System.Collections.Concurrent.Tests.dll -notrait catego
  ry=OuterLoop -notrait category=failing
    info: 17:58:28.0757335 Running "C:\\Users\\rodo\\.jsvu\\jsc.cmd" runtime.js -- --run WasmTestRunner.dll System.Collections.Concurrent.Tests.dll -notrait categ
  ory=OuterLoop -notrait category=failing

    info: console.info: Arguments: --run,WasmTestRunner.dll,System.Collections.Concurrent.Tests.dll,-notrait,category=OuterLoop,-notrait,category=failing
    info: ABORT: no native wasm support detected
    info: Stacktrace:
    info:
    info: onAbort@runtime.js:217:22
    info: abort@dotnet.js:1450:22
    info: global code@dotnet.js:596:8
    info: load@[native code]
    info: loadScript@runtime.js:203:7
    info: global code@runtime.js:287:11
    info: Exception: TypeError: Module.wasm_exit  is not a function. (In 'Module.wasm_exit (exit_code)', 'Module.wasm_exit ' is undefined)
    info: test_exit@runtime.js:128:19
    info: onAbort@runtime.js:220:12
    info: abort@dotnet.js:1450:22
    info: global code@dotnet.js:596:8
    info: load@[native code]
    info: loadScript@runtime.js:203:7
    info: global code@runtime.js:287:11
    info: 17:58:28.2185445 Process jsc.cmd exited with 3

    fail: Application has finished with exit code 3 but 0 was expected
    XHarness exit code: 71 (GENERAL_FAILURE)
ghost commented 3 years ago

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

Issue Details
The library tests are failing on Windows with JavaScriptCore. We are ignoring it for now, this issue is a reminder to look into it later. ``` XHarness command issued: wasm test --app=. --engine=javascriptcore --js-file=runtime.js --output-directory=C:\Users\rodo\git\runtime\artifacts\bin\System.Coll ections.Concurrent.Tests\net6.0-Debug\browser-wasm\AppBundle\xharness-output -- --run WasmTestRunner.dll System.Collections.Concurrent.Tests.dll -notrait catego ry=OuterLoop -notrait category=failing info: 17:58:28.0757335 Running "C:\\Users\\rodo\\.jsvu\\jsc.cmd" runtime.js -- --run WasmTestRunner.dll System.Collections.Concurrent.Tests.dll -notrait categ ory=OuterLoop -notrait category=failing info: console.info: Arguments: --run,WasmTestRunner.dll,System.Collections.Concurrent.Tests.dll,-notrait,category=OuterLoop,-notrait,category=failing info: ABORT: no native wasm support detected info: Stacktrace: info: info: onAbort@runtime.js:217:22 info: abort@dotnet.js:1450:22 info: global code@dotnet.js:596:8 info: load@[native code] info: loadScript@runtime.js:203:7 info: global code@runtime.js:287:11 info: Exception: TypeError: Module.wasm_exit is not a function. (In 'Module.wasm_exit (exit_code)', 'Module.wasm_exit ' is undefined) info: test_exit@runtime.js:128:19 info: onAbort@runtime.js:220:12 info: abort@dotnet.js:1450:22 info: global code@dotnet.js:596:8 info: load@[native code] info: loadScript@runtime.js:203:7 info: global code@runtime.js:287:11 info: 17:58:28.2185445 Process jsc.cmd exited with 3 fail: Application has finished with exit code 3 but 0 was expected XHarness exit code: 71 (GENERAL_FAILURE) ```
Author: radekdoulik
Assignees: radekdoulik
Labels: `arch-wasm`
Milestone: Future
dotnet-issue-labeler[bot] commented 3 years ago

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 commented 3 years ago

Tagging subscribers to this area: @CoffeeFlux See info in area-owners.md if you want to be subscribed.

Issue Details
The library tests are failing on Windows with JavaScriptCore. We are ignoring it for now, this issue is a reminder to look into it later. ``` XHarness command issued: wasm test --app=. --engine=javascriptcore --js-file=runtime.js --output-directory=C:\Users\rodo\git\runtime\artifacts\bin\System.Coll ections.Concurrent.Tests\net6.0-Debug\browser-wasm\AppBundle\xharness-output -- --run WasmTestRunner.dll System.Collections.Concurrent.Tests.dll -notrait catego ry=OuterLoop -notrait category=failing info: 17:58:28.0757335 Running "C:\\Users\\rodo\\.jsvu\\jsc.cmd" runtime.js -- --run WasmTestRunner.dll System.Collections.Concurrent.Tests.dll -notrait categ ory=OuterLoop -notrait category=failing info: console.info: Arguments: --run,WasmTestRunner.dll,System.Collections.Concurrent.Tests.dll,-notrait,category=OuterLoop,-notrait,category=failing info: ABORT: no native wasm support detected info: Stacktrace: info: info: onAbort@runtime.js:217:22 info: abort@dotnet.js:1450:22 info: global code@dotnet.js:596:8 info: load@[native code] info: loadScript@runtime.js:203:7 info: global code@runtime.js:287:11 info: Exception: TypeError: Module.wasm_exit is not a function. (In 'Module.wasm_exit (exit_code)', 'Module.wasm_exit ' is undefined) info: test_exit@runtime.js:128:19 info: onAbort@runtime.js:220:12 info: abort@dotnet.js:1450:22 info: global code@dotnet.js:596:8 info: load@[native code] info: loadScript@runtime.js:203:7 info: global code@runtime.js:287:11 info: 17:58:28.2185445 Process jsc.cmd exited with 3 fail: Application has finished with exit code 3 but 0 was expected XHarness exit code: 71 (GENERAL_FAILURE) ```
Author: radekdoulik
Assignees: radekdoulik
Labels: `arch-wasm`, `area-VM-meta-mono`
Milestone: Future