a2e71dafac
This commit attempts to slim down our CI (more from #2933) by removing testing both in debug and release mode. I can't actually recall a concrete issue that this has turned up on CI itself, and otherwise we're spending quite a lot of time building all of the dev-dependencies in release mode when testing. Additionally it removes testing for nightly/beta channels of Rust. One of the main benefits of this, staying on top of breakage, is already moot because we pin to a nightly anyway. We have a few nightly references elsewhere in CI (fuzzing/docs) so we can largely rely on that (and upstream testing with rust-lang/rust). We in general shouldn't need to do nightly/beta testing on all builds. The release builders were actually the only location that MinGW and AArch64 was tested however. This means that the old nightly/beta builders are now replaced with AArch64 and MinGW builders. Overall, the changes made to CI here are: * Upgrade to QEMU 6.0.0. I thought this would make aarch64 emulation faster, but it didn't. Seems good to stay up to date though. * Replace nightly/beta testing in debug mode with MinGW and AArch64 testing. * Use `-g0` for C compilation on MinGW because otherwise `gcc` as used on CI generates an ICE (!!) * Exclude `wasi-crypto` from testing. We already exclude `wasmtime-wasi-crypto` and it was an accident we were testing the `wasi-crypto` crate (which isn't even part of this workspace). * Remove testing DWARF on the old backend step, which nowadays didn't actually do that. * Remove testing on release builders, making then purely tasked with release builds, nothing else. * Rename `QEMU_VERSION` to `QEMU_BUILD_VERSION` so qemu doesn't just immediately exit after printing its version. Timing wise the release builds are ~20-30 minutes faster, depending on the platform. This is not really because of testing time but rather we have a huge dependency tree when `dev-dependencies` are considered (criterion, tokio, proptest, ...). MinGW tests are pretty fast since we don't run examples (we're not too interested in doing examples there, just windows/mac/linux coverage). AArch64 tests are run with optimizations enabled because unoptimized tests take ~45 minutes to finish while optimized tests take ~20 minutes. The build is naturally much faster in debug mode but apparently under QEMU emulation the debug mode binaries are *extremely* slow compared to the release binaries, which means that extra time we spend compiling release tests is more than made up by faster test emulation time. Closes #2938
wasmtime
A standalone runtime for WebAssembly
A Bytecode Alliance project
Guide | Contributing | Website | Chat
Installation
The Wasmtime CLI can be installed on Linux and macOS with a small install script:
$ curl https://wasmtime.dev/install.sh -sSf | bash
Windows or otherwise interested users can download installers and binaries directly from the GitHub Releases page.
Example
If you've got the Rust compiler installed then you can take some Rust source code:
fn main() {
println!("Hello, world!");
}
and compile/run it with:
$ rustup target add wasm32-wasi
$ rustc hello.rs --target wasm32-wasi
$ wasmtime hello.wasm
Hello, world!
Features
-
Lightweight. Wasmtime is a standalone runtime for WebAssembly that scales with your needs. It fits on tiny chips as well as makes use of huge servers. Wasmtime can be embedded into almost any application too.
-
Fast. Wasmtime is built on the optimizing Cranelift code generator to quickly generate high-quality machine code at runtime.
-
Configurable. Whether you need to precompile your wasm ahead of time, generate code blazingly fast with Lightbeam, or interpret it at runtime, Wasmtime has you covered for all your wasm-executing needs.
-
WASI. Wasmtime supports a rich set of APIs for interacting with the host environment through the WASI standard.
-
Standards Compliant. Wasmtime passes the official WebAssembly test suite, implements the official C API of wasm, and implements future proposals to WebAssembly as well. Wasmtime developers are intimately engaged with the WebAssembly standards process all along the way too.
Language Support
You can use Wasmtime from a variety of different languages through embeddings of the implementation:
- Rust - the
wasmtimecrate - C - the
wasm.h,wasi.h, andwasmtime.hheaders - Python - the
wasmtimePyPI package - .NET - the
WasmtimeNuGet package - Go - the
wasmtime-gorepository
Documentation
📚 Read the Wasmtime guide here! 📚
The wasmtime guide is the best starting point to learn about what Wasmtime can do for you or help answer your questions about Wasmtime. If you're curious in contributing to Wasmtime, it can also help you do that!
It's Wasmtime.