* Run asan with `-Zbuild-std`
* Run Rust tests using Valgrind and cargo-careful.
* Pin Valgrind task to 1.61.0 to avoid the DWARF5 issues until fixed upstream.
* Override output checking of compilation UI tests as using different Rust versions might break that.
Co-authored-by: messense <messense@icloud.com>
* xtask: move coverage implementation to nox
* move pytests from xtask to nox in ci
* use --package instead of --manifest-path for tests
* write github actions groups to sys.stderr
* ci: test on emscripten target
This adds CI to build libpython3.11 for wasm32-emscripten and
running tests against it. We need to patch instant to work
around the emscripten_get_now:
https://github.com/sebcrozet/instant/pull/47
We also have to patch emscripten to work aroung the "undefined
symbol gxx_personality_v0" error:
https://github.com/emscripten-core/emscripten/issues/17128
I set up a nox file to download and install emscripten,
download and build cpython, set appropriate environment variables
then run cargo test. The workflow just installs python, rust,
node, and nox and runs the nox session.
I xfailed all the test failures. There are problems with datetime.
iter_dict_nosegv and test_filenotfounderror should probably be
fixable. The tests that involve threads or asyncio probably can't
be fixed.
* Some cleanup
* Remove instant patch
* Add explanations for xfails
David Hewitt