Stream: git-wasmtime

Topic: wasmtime / issue #11385 Wasmtime runtime returns invalid ...

view this post on Zulip Wasmtime GitHub notifications bot (Aug 06 2025 at 03:12):

Theaamadu opened issue #11385:

Test Case

Wasm file:

wasm-shrunken_199-clock_gettime-monotonic.txt

Wat file:

wat-shrunken_199-clock_gettime-monotonic.txt

Steps to Reproduce

  1. Run command: wasmtime run -W all-proposals=y --invoke _start $wasm_file

Expected Results

Based on the results of other runtimes, wasmtime should also have a timeout

Actual Results

Wasmtime returns Invalid enum value Clockid error

Versions and Environment

wasmtime 36.0.0 (bdb963d1f 2025-07-07)

Operating system: Ubuntu 22.04

Architecture: X86_64

Extra Info

I must say that I have reduced the size of the both wat & wasm code to my best. Could you please confirm the bug? Thanks

view this post on Zulip Wasmtime GitHub notifications bot (Aug 06 2025 at 03:12):

Theaamadu added the bug label to Issue #11385.

view this post on Zulip Wasmtime GitHub notifications bot (Aug 06 2025 at 14:47):

alexcrichton commented on issue #11385:

Can you explain more about why you feel this is a bug? For example how was this source generate? Fuzz-generated? Minimized from C? Edge-case behavior of WASI varies runtime-to-runtime as the precise semantics of WASI have evolved over time. For WASIp1 there is no more development and much of its APIs are under-specified as the eventual work that would have gone into specifying them went into the component model instead.

My guess is this is likely not a bug in Wasmtime but probably a difference in validation of parameters with other runtimes. For example other runtimes may generate a different error first and/or skip validation that should be required. Understanding the provenance of this program and what it's trying to do is going to be key in understanding what exactly is the desired output of this program. Minimized *.wat code generally isn't too helpful for WASI APIs, it's best to start from a source language if possible (e.g. there's nothing to debug with in the files you posted)

view this post on Zulip Wasmtime GitHub notifications bot (Aug 06 2025 at 14:47):

alexcrichton added the wasi label to Issue #11385.

view this post on Zulip Wasmtime GitHub notifications bot (Aug 06 2025 at 14:47):

alexcrichton removed the bug label from Issue #11385.

view this post on Zulip Wasmtime GitHub notifications bot (Aug 21 2025 at 23:08):

alexcrichton closed issue #11385:

Test Case

Wasm file:

wasm-shrunken_199-clock_gettime-monotonic.txt

Wat file:

wat-shrunken_199-clock_gettime-monotonic.txt

Steps to Reproduce

  1. Run command: wasmtime run -W all-proposals=y --invoke _start $wasm_file

Expected Results

Based on the results of other runtimes, wasmtime should also have a timeout

Actual Results

Wasmtime returns Invalid enum value Clockid error

Versions and Environment

wasmtime 36.0.0 (bdb963d1f 2025-07-07)

Operating system: Ubuntu 22.04

Architecture: X86_64

Extra Info

I must say that I have reduced the size of the both wat & wasm code to my best. Could you please confirm the bug? Thanks

view this post on Zulip Wasmtime GitHub notifications bot (Aug 21 2025 at 23:08):

alexcrichton commented on issue #11385:

Haven't heard back in awhile so I'm going to close this, but happy to reopen if more information comes to light.

Last updated: Dec 06 2025 at 07:03 UTC