Changes in build.rs

daee7fda - Introduce `wasmtime_environ::collections::{OomArc, OomBox}` (#12361)

Wed, 21 Jan 2026 18:40:24 +0000

Introduce `wasmtime_environ::collections::{OomArc, OomBox}` (#12361)* Introduce `wasmtime_environ::collections::{OomArc, OomBox}`These types mirror their `std`/`alloc` counterparts, but only provide fallibleconstructors and properly handle OOM by returning `Err(OutOfMemory)`.Note that stable Rust doesn't actually give us any method to build fallibleallocation for `Arc`, and we do not wish to fork `Arc` since it is full ofvery subtle unsafe code, so `OomArc::new` is only actually fallible in practicewhen using nightly Rust and setting `RUSTFLAGS="--cfg arc_try_new"` during thebuild. We use a custom `cfg`, rather than a cargo feature, so that `cargo test--all-features --workspace` (which is morally what CI does) continues to JustWork in the workspace, same as we do for e.g. Pulley's usage of the nightly Rusttail calls feature.Part of https://github.com/bytecodealliance/wasmtime/issues/12069* Avoid unused import warning in certain build configs* Remove `out_of_line_slow_path!` macro* Use extension traits for fallible `Arc` and `Box` allocationInstead of defining new wrapper types around them.* Fix example in docs List of files: /wasmtime-44.0.1/crates/fuzzing/build.rs

ca7081a2 - Consolidate "util" crates for testing (#10423)

Thu, 20 Mar 2025 15:08:47 +0000

Consolidate "util" crates for testing (#10423)* Consolidate "util" crates for testingThis commit consolidates all of the existing crates we have for testinginto a smaller set of crates. Specifically:* `crates/misc/component-fuzz-util` => `wasmtime-test-util` + `component-fuzz` feature* `crates/misc/component-test-util` => `wasmtime-test-util` + `component` feature* `crates/wast-util` => `wasmtime-test-util` + `wast` feature* `crates/misc/component-macro-test` => `wasmtime-test-macros`The goal is to have one location we put various test helpers/macrosrather than our current organically-grown many locations. This isinspired by the test failure on #10405 where I'd like to refactor moreinfrastructure to a "test util" location but it wasn't clear where toput it so I wanted to do this refactoring first.* Remove unused file List of files: /wasmtime-44.0.1/crates/fuzzing/build.rs

e9cc928f - Fix minor wast fuzzing issues (#9764)

Tue, 10 Dec 2024 14:15:09 +0000

Fix minor wast fuzzing issues (#9764)* Sort tests by name to ensure that a reproduction on one machine works on another.* Relax the error message matching to be a bit more lenient with paths. List of files: /wasmtime-44.0.1/crates/fuzzing/build.rs

f406347a - Improve fuzzing of `*.wast` tests (#9587)

Mon, 11 Nov 2024 21:00:34 +0000

Improve fuzzing of `*.wast` tests (#9587)* Improve fuzzing of `*.wast` testsCurrently we have a fuzzer which is tasked with running `*.wast` testswith fuzz-generated configurations. This asserts that we at leastsatisfy all basic wasm semantics regardless of how various knobs in`Config` are turned (modulo limits to resources). The current fuzzingthough is not comprehensive in that it doesn't include all the spectests that we pass from all proposals. This runs the risk of we don'tactually fuzz anything until the spec tests are merged upstream, whichcan take a significant amount of time.This commit refactors the `*.wast`-management infrastructure to sharetest discovery and feature calculation between `tests/wast.rs` andfuzzing. This new support crate centralizes limits and discovery forboth to use. Additionally fuzzing is updated to no longer throw out testcases if configuration isn't applicable but instead clamp configurationto the minimum required values (e.g. features + resource limits). Thismeans that we should now be fuzzing all spec tests that pass in allconfigurations.This new fuzzer discovered a few minor issues with the GC proposalimplementation, for example, such as:* Some instructions were translated using trapping methods directly on `FunctionBuilder` rather than `FuncEnvironment` meaning they didn't properly handle `signals-based-traps` configuration.* Fuel handling for `return_call_ref` wasn't correct because it was accidentally omitted from the list of return-call instructions that need special treatment.* Add some manifest metadata List of files: /wasmtime-44.0.1/crates/fuzzing/build.rs

a0442ea0 - Enforce `uninlined_format_args` for the workspace (#9065)

Mon, 05 Aug 2024 09:59:59 +0000

Enforce `uninlined_format_args` for the workspace (#9065)* Enforce `uninlined_format_args` for the workspace* fix: failing `Monolith Checks` job* fix: formatting List of files: /wasmtime-44.0.1/crates/fuzzing/build.rs

1898b8c7 - Run all `*.wast` tests in fuzzing (#8121)

Wed, 13 Mar 2024 20:39:03 +0000

Run all `*.wast` tests in fuzzing (#8121)* Run all `*.wast` tests in fuzzingCurrently we have a `spectest` fuzzer which uses fuzz input to generatean arbitrary configuration for Wasmtime and then executes the spec test.This ensures that no matter the configuration Wasmtime can pass spectests. This commit expands this testing to include all `*.wast` tests wehave in this repository. While we don't have a ton we still have somesignificant ones like in #8118 which will only reproduce when turningknobs on CPU features.* Fix CLI build* Fix wast testing List of files: /wasmtime-44.0.1/crates/fuzzing/build.rs

b1a3c904 - Actually make spectest fuzzing deterministic

Mon, 29 Mar 2021 15:23:23 +0000

Actually make spectest fuzzing deterministicTurns out #2106 missed the actual sorting operation. Silly me! List of files: /wasmtime-44.0.1/crates/fuzzing/build.rs

d6f64ec8 - Make spectest fuzzing more deterministic

Thu, 06 Aug 2020 15:08:20 +0000

Make spectest fuzzing more deterministicCurrently spectest fuzzing indexes into a compile-time-created array ofstrings which is the list of input files, but the order of this array isdependent on the filesystem that we're reading from. This means thatinputs from oss-fuzz may not be easily reproducible locally becausefiles could be read in different orders, so indexes could be distinct.This commit instead reads the directory paths, then sorts them, thenincludes them for testing. That way fuzz inputs at a specific commitshould be consistent. List of files: /wasmtime-44.0.1/crates/fuzzing/build.rs

6dde2229 - Add a spec test fuzzer for Config (#1509)

Wed, 15 Apr 2020 13:29:12 +0000

Add a spec test fuzzer for Config (#1509)* Add a spec test fuzzer for Config This commit adds a new fuzzer which is intended to run on oss-fuzz. This fuzzer creates and arbitrary `Config` which *should* pass spec tests and then asserts that it does so. The goal here is to weed out any accidental bugs in global configuration which could cause non-spec-compliant behavior. * Move implementation to `fuzzing` crate List of files: /wasmtime-44.0.1/crates/fuzzing/build.rs