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.
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
x/build/env/wasip1-wasm-wazero: wasip1 tests are failing #61043
Comments
Change https://go.dev/cl/506695 mentions this issue: |
The current version of the wazero runtime has a known issue surrounding nonblocking I/O. Add a reference to the tracking issue. For golang/go#61043 Change-Id: Ic460058736b99bcf4e2a426924228ed1e2fb6c01 Reviewed-on: https://go-review.googlesource.com/c/build/+/506695 Reviewed-by: Cherry Mui <cherryyz@google.com> Auto-Submit: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com> Run-TryBot: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com>
The wazero issue has been closed and will be available in the next release. We'll upgrade the Wazero runner and hopefully close this issue then. |
The tests pass locally for me with the new wazero version |
Change https://go.dev/cl/508875 mentions this issue: |
The latest version of wazero contains a proposed fix for an I/O bug that is causing build failures. For golang/go#61043 Change-Id: Ifd7d5b0f6d36d52692b22faa85ecfd1a7d385781 Reviewed-on: https://go-review.googlesource.com/c/build/+/508875 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com> Reviewed-by: Cherry Mui <cherryyz@google.com> Reviewed-by: Heschi Kreinick <heschi@google.com> Auto-Submit: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com>
It seems this isn't quite fixed yet in Wazero v1.3.0, I've posted an update to the original issue. |
Change https://go.dev/cl/512255 mentions this issue: |
The latest version of wazero contains a proposed fix for an I/O bug that is causing build failures. For golang/go#61043 Change-Id: Ibcd77469969b51c34c1ae94d6a670a6e86025147 Reviewed-on: https://go-review.googlesource.com/c/build/+/512255 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Auto-Submit: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Cherry Mui <cherryyz@google.com>
Found new dashboard test flakes for:
2023-07-14 12:49 wasip1-wasm-wazero go@c30faf9c test.Test (log)
2023-07-14 17:30 wasip1-wasm-wazero go@847d40d6 test.Test (log)
|
@cherrymui are these errors still happening with the new version deployed? |
I deployed the new version. So far there is only one run after it is deployed and the test passes. So it looks promising. If it passes consistently after a few more runs, we can call it fixed. Thanks! |
Thanks @johanbrandhorst! This issue is still referenced as a "known issue" in x/build/dashboard (here). Since you've marked this as closed, please also remove it there. Thanks. |
Change https://go.dev/cl/513055 mentions this issue: |
The issue has been resolved. For golang/go#61043 Change-Id: Ia3c4223fec18c7987c30f154346222391a969e4e Reviewed-on: https://go-review.googlesource.com/c/build/+/513055 Reviewed-by: Cherry Mui <cherryyz@google.com> Auto-Submit: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
Found new dashboard test flakes for:
2023-07-12 21:23 wasip1-wasm-wazero go@cc0cb302 test.Test (log)
2023-07-13 16:46 wasip1-wasm-wazero go@9480b4ad test.Test (log)
|
These last two flakes are from June, it's likely the same bug that should be fixed. |
After enabling nonblocking io on stdin, stdout and stderr in CL 498196, the wazero wasip1 runner started to fail. The errors look like this:
Sample error log.
The link to the standard I/O change seems pretty clear, but the cause is likely a runtime bug. An issue has been filed with the wazero runtime project. The fix will likely be an update to the wazero version used in the builders.
The wasmtime runner continues to pass all tests as expected.
The text was updated successfully, but these errors were encountered: