Stream: git-wasmtime

Topic: wasmtime / Issue #2706 Properly gate symlink-related unit...

Wasmtime GitHub notifications bot (Mar 04 2021 at 18:04):

cfallin opened Issue #2706:

As per conversation with @sunfishcode just now, it seems that some WASI-related unit test failures I was seeing on MinGW and worked around in #2678 were due to a peculiarity of Windows symlink support: creating symlinks requires enabling Developer Mode, which is not the default setting (and was not enabled on my machine). There is some config plumbing in cap-std to determine if symlinks are supported; we should do the same in wasmtime so that developers can run the full test suite without non-default options.

Wasmtime GitHub notifications bot (Mar 04 2021 at 18:08):

sunfishcode labeled Issue #2706:

As per conversation with @sunfishcode just now, it seems that some WASI-related unit test failures I was seeing on MinGW and worked around in #2678 were due to a peculiarity of Windows symlink support: creating symlinks requires enabling Developer Mode, which is not the default setting (and was not enabled on my machine). There is some config plumbing in cap-std to determine if symlinks are supported; we should do the same in wasmtime so that developers can run the full test suite without non-default options.

Last updated: Nov 22 2024 at 16:03 UTC