Andy Wingo

Tests working on MacOS/Windows/Ubuntu; comment from pchickey not yet addressed

I think these are mostly "expected an error but not that one" failures; given that it's WASIp1, I suggest that we just relax those tests, as a first approach. I.e....

The test log on Windows: ``` Test filesystem-flags-and-type failed [exit_code] 0 == 3 STDOUT: STDERR: thread '' (1) panicked at src/bin/filesystem-flags-and-type.rs:55:14: called `Result::unwrap_err()` on an `Ok` value: Descriptor { handle:...

The file: https://github.com/WebAssembly/wasi-testsuite/blob/main/tests/rust/wasm32-wasip3/src/bin/filesystem-flags-and-type.rs

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

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.

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

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

Windows 11 on ARM is the same as normal windows.

Wasmtime fails the same wasip1 test on MacOS as it does on Windows: https://github.com/bytecodealliance/wasmtime/issues/11524