Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[WASI] Sockets - unknown handle index #108726

Open
ericstj opened this issue Oct 9, 2024 · 4 comments
Open

[WASI] Sockets - unknown handle index #108726

ericstj opened this issue Oct 9, 2024 · 4 comments
Assignees
@pavelsavara
Labels
arch-wasm WebAssembly architecture area-System.Net blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' Known Build Error Use this to report build issues in the .NET Helix tab os-wasi Related to WASI variant of arch-wasm
Milestone
10.0.0

Comments

@ericstj
Copy link
Member

ericstj commented Oct 9, 2024 •
edited by build-analysis bot
Loading

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=835727
Build error leg or test failing: System.Net.Sockets.Tests.WorkItemExecution
Pull request: #108718

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": ["info: Starting:    managed/System.Net.Sockets.Tests.dll", "Error: failed to run main module `dotnet.wasm`"],
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-pull-108718-merge-4274d6dbf69d44e5a7/System.Net.Sockets.Tests/1/console.57a801cd.log?helixlogtype=result

[20:23:20] info: Error: failed to run main module `dotnet.wasm`
[20:23:20] info: 
[20:23:20] info: Caused by:
[20:23:20] info:     0: failed to invoke `run` function
[20:23:20] info:     1: error while executing at wasm backtrace:
[20:23:20] info:            0: 0x38db25 - wit-component:shim!indirect-wasi:io/[email protected]
[20:23:20] info:            1: 0x23f38 - <unknown>!<wasm function 311>
[20:23:20] info:            2: 0x22950 - <unknown>!<wasm function 286>
[20:23:20] info:            3: 0x1222b - <unknown>!<wasm function 234>
[20:23:20] info:            4: 0x10e6f - <unknown>!<wasm function 233>
[20:23:20] info:            5: 0x13d96a - <unknown>!<wasm function 4274>
[20:23:20] info:            6: 0xfd1c6 - <unknown>!<wasm function 3199>
[20:23:20] info:            7: 0xfdcc7 - <unknown>!<wasm function 3208>
[20:23:20] info:            8: 0x102b08 - <unknown>!<wasm function 3281>
[20:23:20] info:            9: 0x1024e3 - <unknown>!<wasm function 3278>
[20:23:20] info:           10: 0xf566 - <unknown>!<wasm function 199>
[20:23:20] info:           11: 0x2947be - <unknown>!<wasm function 11646>
[20:23:20] info:           12: 0xaadf - <unknown>!<wasm function 129>
[20:23:20] info:           13: 0x38557a - wit-component:adapter:wasi_snapshot_preview1!wasi:cli/[email protected]#run
[20:23:20] info:     2: unknown handle index 0
[20:23:20] info: Process wasmtime.exe exited with 1
[20:23:20] info: Waiting to flush log messages with a timeout of 120 secs ..
[20:23:20] fail: Application has finished with exit code 1 but 0 was expected
XHarness exit code: 71 (GENERAL_FAILURE)

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=835727
Error message validated: [info: Starting: managed/System.Net.Sockets.Tests.dll Error: failed to run main module dotnet.wasm``]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 10/9/2024 8:38:46 PM UTC

Report

Build Definition Test Pull Request
947375 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #111307
947366 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #112209
946641 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #112256
946285 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #112337
946066 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #111598
945538 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution
945437 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #112209
944205 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #112199
941742 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #112201
941493 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #111091
941378 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #107769
938332 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #96895
935218 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #111318
935195 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #111990
934998 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #111604
934317 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #111938
933488 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #111953
933405 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #111952
931603 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #111886
930568 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #111858
926883 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #111754
926564 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #111747
925783 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #111677
925717 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #111722
925743 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #109928
925683 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution
925238 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #111215
924364 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #111209
924247 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #111505
921287 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #111549
920078 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #111472
920069 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #111505
919902 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #111311
919870 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #111245
919553 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution
918585 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #111032
917091 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #111041
916343 dotnet/runtime System.Net.Sockets.Tests.WorkItemExecution #111323

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 11 38
@ericstj ericstj added blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' Known Build Error Use this to report build issues in the .NET Helix tab labels Oct 9, 2024
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Oct 9, 2024
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Oct 9, 2024
@ericstj ericstj added arch-wasm WebAssembly architecture area-System.Net os-wasi Related to WASI variant of arch-wasm and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Oct 9, 2024
@dotnet-policy-service Dotnet Policy Service
Copy link
Contributor

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

@dotnet-policy-service Dotnet Policy Service
Copy link
Contributor

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

@lewing lewing added this to the 10.0.0 milestone Oct 9, 2024
@dotnet-policy-service dotnet-policy-service bot removed the untriaged New issue has not been triaged by the area owner label Oct 9, 2024
@pavelsavara
Copy link
Member

Also handle -1

Log

[07:17:01] info: [STRT] System.Net.Sockets.Tests.NetworkStreamTest.NetworkStream_ReadAsyncTimeout_RemainUseable
[07:17:01] info: Error: failed to run main module `dotnet.wasm`
[07:17:01] info: 
[07:17:01] info: Caused by:
[07:17:01] info:     0: failed to invoke `run` function
[07:17:01] info:     1: error while executing at wasm backtrace:
[07:17:01] info:            0: 0x38d0cb - wit-component:shim!indirect-wasi:io/[email protected]
[07:17:01] info:            1: 0x23d84 - <unknown>!<wasm function 310>
[07:17:01] info:            2: 0x2279c - <unknown>!<wasm function 285>
[07:17:01] info:            3: 0x1209e - <unknown>!<wasm function 233>
[07:17:01] info:            4: 0x10cc4 - <unknown>!<wasm function 232>
[07:17:01] info:            5: 0x1397e0 - <unknown>!<wasm function 4241>
[07:17:01] info:            6: 0xfa49c - <unknown>!<wasm function 3175>
[07:17:01] info:            7: 0xfaf9d - <unknown>!<wasm function 3184>
[07:17:01] info:            8: 0xffdde - <unknown>!<wasm function 3257>
[07:17:01] info:            9: 0xff7b9 - <unknown>!<wasm function 3254>
[07:17:01] info:           10: 0xf3ae - <unknown>!<wasm function 198>
[07:17:01] info:           11: 0x29476b - <unknown>!<wasm function 11616>
[07:17:01] info:           12: 0xaa53 - <unknown>!<wasm function 128>
[07:17:01] info:           13: 0x384b45 - wit-component:adapter:wasi_snapshot_preview1!wasi:cli/[email protected]#run
[07:17:01] info:     2: unknown handle index 4294967295

Maybe something about how SafeHandle is GC'ed

@pavelsavara pavelsavara changed the title Sockets tests failing on wasi-wasm [WASI] Sockets - unknown handle index Dec 9, 2024
@max-charlamb max-charlamb mentioned this issue Dec 13, 2024
Merged
5 tasks
@pavelsavara
Copy link
Member

another with negative handle

Log

[13:58:18] info: [STRT] System.Net.Sockets.Tests.ReceiveMessageFrom_MemoryNativeTask.ClosedDuringOperation_Throws_ObjectDisposedExceptionOrSocketException(closeOrDispose: True)
[13:58:18] info: Error: failed to run main module `dotnet.wasm`
[13:58:18] info: 
[13:58:18] info: Caused by:
[13:58:18] info:     0: failed to invoke `run` function
[13:58:18] info:     1: error while executing at wasm backtrace:
[13:58:18] info:            0: 0x38cc5d - wit-component:shim!indirect-wasi:io/[email protected]
[13:58:18] info:            1: 0x23d2b - <unknown>!<wasm function 310>
[13:58:18] info:            2: 0x22708 - <unknown>!<wasm function 285>
[13:58:18] info:            3: 0x1209b - <unknown>!<wasm function 233>
[13:58:18] info:            4: 0x10cc4 - <unknown>!<wasm function 232>
[13:58:18] info:            5: 0x138fa9 - <unknown>!<wasm function 4240>
[13:58:18] info:            6: 0xf9d8f - <unknown>!<wasm function 3174>
[13:58:18] info:            7: 0xfa89f - <unknown>!<wasm function 3183>
[13:58:18] info:            8: 0xff69d - <unknown>!<wasm function 3256>
[13:58:18] info:            9: 0xff07b - <unknown>!<wasm function 3253>
[13:58:18] info:           10: 0xf3cb - <unknown>!<wasm function 198>
[13:58:18] info:           11: 0x293dad - <unknown>!<wasm function 11616>
[13:58:18] info:           12: 0xaa4d - <unknown>!<wasm function 128>
[13:58:18] info:           13: 0x3846d6 - wit-component:adapter:wasi_snapshot_preview1!wasi:cli/[email protected]#run
[13:58:18] info:     2: unknown handle index 4294967295

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pavelsavara pavelsavara

Labels
arch-wasm WebAssembly architecture area-System.Net blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' Known Build Error Use this to report build issues in the .NET Helix tab os-wasi Related to WASI variant of arch-wasm
Projects
None yet
Milestone
10.0.0
Development

No branches or pull requests
3 participants
@lewing @pavelsavara @ericstj