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.
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.