Newly added WASIp3 tests failing

[wingo]

There are only like 7 WASIp3 tests in the repo but not all are passing everywhere. This issue is a tracker to fix this situation.

There used to be more details here but it was messy and path-dependent and we fixed a few issues. Now the problems are all in the sub-issues listed below. Leaving the comments as they were, but to see the original description, look in the history.

[wingo]

My goodness this thing is complicated: main branch, prod/testsuite-base branch, copies of file trees from source dirs to object file dirs, github artifacts per language that the test is written in... I think the copytree works fine, but the upload-artifact doesn't propagate the dangling symlinks.

[wingo]

So now we add another layer of complexity in #174, tarballing the rust tests. Annoying, but it fixes everything but the HTTP test on Ubuntu.

[wingo]

Now let's look beyond Ubuntu. On MacOS:

filesystem-advise.rs

https://github.com/WebAssembly/wasi-testsuite/actions/runs/18308851626/job/52132549810?pr=174#step:12:128

fadvise(7, 0, Advice::WillNeed) => file-too-large (error 7).

[wingo]

x86-64 windows:

filesystem-flags-and-type.rs

https://github.com/WebAssembly/wasi-testsuite/actions/runs/18308851626/job/52132549816?pr=174#step:12:1320

No error where error expected at filesystem-flags-and-type.rs:55:14. Moved to #176.

filesystem-hard-links.rs

https://github.com/WebAssembly/wasi-testsuite/actions/runs/18308851626/job/52132549816?pr=174#step:12:1368

Unexpected error: EACCESS instead of expected EPERM. Moved to #177.

[wingo]

Windows 11 on ARM is the same as normal windows.

[wingo]

Wasmtime fails the same wasip1 test on MacOS as it does on Windows: bytecodealliance/wasmtime#11524

[wingo]

On Windows, wasmtime fails 36 wasip1 tests in addition to the 3 wasip3 tests mentioned above. Log file from https://github.com/WebAssembly/wasi-testsuite/actions/runs/18305522215/job/52121798099 attached, just in case it goes away.

run-test-wasmtime-windows.log