Stream: git-wasmtime

Topic: wasmtime / issue #7829 `utime()` does not accept a file d...


view this post on Zulip Wasmtime GitHub notifications bot (Jan 26 2024 at 20:27):

brettcannon added the bug label to Issue #7829.

view this post on Zulip Wasmtime GitHub notifications bot (Jan 26 2024 at 20:27):

brettcannon opened issue #7829:

Test Case

TODO: upload Wasm file here

Steps to Reproduce

Expected Results

Test should pass (it does under preview 1).

Actual Results

Raises errno 63: ENOSR (out of stream resources).

Versions and Environment

Wasmtime version or commit: 17.0.0

Operating system: Linux/WSL

Architecture: x64

Extra Info

Anything else you'd like to add?

Success logs under preview 1:
success-utime-fd.txt

Failure logs under preview 2:
failure-utime-fd.txt

view this post on Zulip Wasmtime GitHub notifications bot (Jan 26 2024 at 21:52):

alexcrichton commented on issue #7829:

Could you perhaps reupload the failure logs? It currently seems to be empty and/or says success with no extra logs

view this post on Zulip Wasmtime GitHub notifications bot (Jan 26 2024 at 23:31):

brettcannon commented on issue #7829:

failure-utime-fd.txt

Sorry about that!

view this post on Zulip Wasmtime GitHub notifications bot (Feb 06 2024 at 00:51):

pchickey commented on issue #7829:

@elliottt and I investigated this and will be posting a fix shortly.

view this post on Zulip Wasmtime GitHub notifications bot (Feb 06 2024 at 01:15):

pchickey commented on issue #7829:

@brettcannon We read the test source you linked to and believed we reproduced it in PR #7876 with a modification to one of our existing tests, and then fixed it in the same PR. I don't know how to run your tests locally to verify that this fixed it, but we think we got the underlying bug in our implementation fixed now. Please verify for us whether this is a fix when you have time, and also if it changes the status of any other of your posix tests, which exercise a lot more than our test suite.

view this post on Zulip Wasmtime GitHub notifications bot (Feb 06 2024 at 18:45):

brettcannon commented on issue #7829:

I don't know how to run your tests locally to verify that this fixed it

FYI I'm working on better docs for this, but https://github.com/python/cpython/tree/main/Tools/wasm#wasi-wasm32-wasi are the current docs if you're interested.

Please verify for us whether this is a fix when you have time

Will do! I'll plan to give it a try this week.

if it changes the status of any other of your posix tests, which exercise a lot more than our test suite.

Yeah, Python's test suite is old and extensive for this sort of thing: we're great at exercising C compilers and OSs. :grinning_face_with_smiling_eyes: If you're ever interested in trying to get the Python test suite set up as a 3rd-party test suite to run, just let me know.

view this post on Zulip Wasmtime GitHub notifications bot (Feb 10 2024 at 01:20):

brettcannon commented on issue #7829:

Commented at https://github.com/bytecodealliance/wasmtime/pull/7876#issuecomment-1936792352 about the PR passing CPython's test suite.

view this post on Zulip Wasmtime GitHub notifications bot (Feb 14 2024 at 21:15):

pchickey closed issue #7829:

Test Case

TODO: upload Wasm file here

Steps to Reproduce

Expected Results

Test should pass (it does under preview 1).

Actual Results

Raises errno 63: ENOSR (out of stream resources).

Versions and Environment

Wasmtime version or commit: 17.0.0

Operating system: Linux/WSL

Architecture: x64

Extra Info

Anything else you'd like to add?

Success logs under preview 1:
success-utime-fd.txt

Failure logs under preview 2:
failure-utime-fd.txt

view this post on Zulip Wasmtime GitHub notifications bot (Feb 14 2024 at 21:15):

pchickey commented on issue #7829:

This landed in main and in release-18.0.0 so I'm going to close it now. We chose not to release this fix as a patch release on release-17.0.0 but if someone really needs it before 18 goes out in 7 days, we still could.


Last updated: Dec 23 2024 at 12:05 UTC