alexcrichton opened issue #11622:
In 2/3 tests I've ported so far I've discovered panics in the runtime for unrelated things. Given that I think we should take a hard requirement on porting all preview1 tests before WASIp3 ships. We didn't do this for WASIp2 but that's because WASIp2 APIs are thoroughly tested via the WASIp1 tests through the adapter. We do not have this luxury for WASIp3 as the adapter is not planned to be implemented for p1-to-p3. Thus this is basically an issue about achieving test parity with WASIp2 for WASIp3.
alexcrichton added the wasi label to Issue #11622.
alexcrichton added the wasm-proposal:component-model-async label to Issue #11622.
alexcrichton commented on issue #11622:
As mentioned in https://github.com/bytecodealliance/wasip3-prototyping/issues/109 this should apply to WASIp2 http tests as well
alexcrichton assigned alexcrichton to issue #11622.
tschneidereit unassigned alexcrichton from issue #11622.
tschneidereit commented on issue #11622:
In discussion with Alex, we agreed that this will adequately be covered by a combination of the WASIp3 test suite work @wingo is doing and adding robust fuzzing for WASIp3.
Last updated: Dec 06 2025 at 06:05 UTC