en Copyright 2015 Java http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/fuzzing/src/generators/wast_test.rs#ca7081a2 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/src/generators/wast_test.rs Thu, 20 Mar 2025 15:08:47 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/fuzzing/src/generators/wast_test.rs#45b60bd6 Start using `#[expect]` instead of `#[allow]` (#9696)* Start using `#[expect]` instead of `#[allow]`In Rust 1.81, our new MSRV, a new feature was added to Rust to use`#[expect]` to control lint levels. This new lint annotation willsilence a lint but will itself cause a lint if it doesn't actuallysilence anything. This is quite useful to ensure that annotations don'tget stale over time.Another feature is the ability to use a `reason` directive on theattribute with a string explaining why the attribute is there. Thisstring is then rendered in compiler messages if a warning or errorhappens.This commit migrates applies a few changes across the workspace:* Some `#[allow]` are changed to `#[expect]` with a `reason`.* Some `#[allow]` have a `reason` added if the lint conditionally fires (mostly related to macros).* Some `#[allow]` are removed since the lint doesn't actually fire.* The workspace configures `clippy::allow_attributes_without_reason = 'warn'` as a "ratchet" to prevent future regressions.* Many crates are annotated to allow `allow_attributes_without_reason` during this transitionary period.The end-state is that all crates should use`#[expect(..., reason = "...")]` for any lint that unconditionally firesbut is expected. The `#[allow(..., reason = "...")]` lint should be usedfor conditionally firing lints, primarily in macro-related code.The `allow_attributes_without_reason = 'warn'` level is intended to bepermanent but the transitionary`#[expect(clippy::allow_attributes_without_reason)]` crate annotationsto go away over time.* Fix adapter buildprtest:full* Fix one-core build of icache coherence* Use `allow` for missing_docsWork around rust-lang/rust#130021 which was fixed in Rust 1.83 and isn'tfixed for our MSRV at this time.* More MSRV compat List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/wast_test.rs Mon, 02 Dec 2024 17:19:20 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/fuzzing/src/generators/wast_test.rs#f406347a 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/src/generators/wast_test.rs Mon, 11 Nov 2024 21:00:34 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/fuzzing/src/generators/wast_test.rs#1898b8c7 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/src/generators/wast_test.rs Wed, 13 Mar 2024 20:39:03 +0000 Alex Crichton <alex@alexcrichton.com>