Stream: git-wasmtime

Topic: wasmtime / issue #11582 P3 async wast test failures

Wasmtime GitHub notifications bot (Sep 02 2025 at 00:00):

lukewagner opened issue #11582:

The following two component-model async tests fail on the current (Sept 28) dev release:

1. tests/async/cancel-subtask.wast

The problem seems to be that the call to waitable-set.wait on line 51 which is defined without cancellable set (on line 64) returns the TASK_CANCELLED code (= 6) when subtask.cancel is called on line 144. Instead, I believe that, since the subtask isn't cancellable, subtask.cancel should immediately return the BLOCKED code (= -1).

2. tests/async/zero-length.wast

The problem seems to be that $consume_cb (defined on line 147) is called with $event_code = STREAM_WRITE (= 3) instead of the expected STREAM_READ (= 2) for the stream.read issued on line 139. Additionally, the $index isn't $insr (= 2), which was passed to stream.read; it's 3. Maybe there's a mixup between the readable and writable ends here?

Wasmtime GitHub notifications bot (Sep 02 2025 at 00:00):

lukewagner added the bug label to Issue #11582.

Wasmtime GitHub notifications bot (Sep 02 2025 at 00:47):

alexcrichton added the wasm-proposal:component-model-async label to Issue #11582.

Wasmtime GitHub notifications bot (Sep 04 2025 at 23:18):

alexcrichton assigned dicej to issue #11582.

Wasmtime GitHub notifications bot (Sep 10 2025 at 21:32):

dicej closed issue #11582:

The following two component-model async tests fail on the current (Sept 28) dev release:

1. tests/async/cancel-subtask.wast

The problem seems to be that the call to waitable-set.wait on line 51 which is defined without cancellable set (on line 64) returns the TASK_CANCELLED code (= 6) when subtask.cancel is called on line 144. Instead, I believe that, since the subtask isn't cancellable, subtask.cancel should immediately return the BLOCKED code (= -1).

2. tests/async/zero-length.wast

The problem seems to be that $consume_cb (defined on line 147) is called with $event_code = STREAM_WRITE (= 3) instead of the expected STREAM_READ (= 2) for the stream.read issued on line 139. Additionally, the $index isn't $insr (= 2), which was passed to stream.read; it's 3. Maybe there's a mixup between the readable and writable ends here?

Wasmtime GitHub notifications bot (Sep 10 2025 at 21:32):

dicej commented on issue #11582:

The first failure is addressed by https://github.com/bytecodealliance/wasmtime/pull/11671 and the second one has apparently been fixed by some other change since this issue was opened :tada:

Last updated: Dec 06 2025 at 06:05 UTC