Changes in Cargo.toml

99507c2c - Consolidate building guest programs for tests (#10654)

Thu, 24 Apr 2025 20:30:00 +0000

Consolidate building guest programs for tests (#10654)* Consolidate building guest programs for testsThis commit folds all C/C++ tests for debuginfo into the same locationas Rust programs compiled to wasm. That means that all of`tests/all/debug/testsuite/*` is moved to`crates/test-programs/src/bin/*`. Additionally the hardcoded per-testconfiguration in `crates/test-programs/artifacts/build.rs` was removedin favor of in-test configuration at the top of the file. This meansthat all precompiled binaries are removed from the tree for DWARFtesting.Various offsets were updated, a test was dropped as it wasn't used, andsome commands/directives were updated to account for this adjustment.prtest:debug* Adjust a lint setting List of files: /wasmtime-44.0.1/crates/test-programs/artifacts/Cargo.toml

8e883429 - Update some dependencies on their major version tracks (#10425)

Thu, 20 Mar 2025 01:40:14 +0000

Update some dependencies on their major version tracks (#10425)* Update rustix to 1.0.x* Bump itertools to its latest version* Update base64 to its latest version* Update wit-bindgen to its latest version* Update v8 to its latest version on crates.ioJust keeping up-to-date* Update capstone dependency to its latest version* Update libtest-mimic to its latest version* Update cargo-metadata dependency* Update thiserror dependency to latest* Update bytesize dependency* Drop getrandom dependency from test-programsFavor using `wasi::random_get` instead for now.* Fix deny.toml syntax* Fix merge conflict* Downgrade v8 to respect MSRV* Fix compile on windows List of files: /wasmtime-44.0.1/crates/test-programs/artifacts/Cargo.toml

83029e3f - Add `rust-version.workspace = true` to all crates (#9112)

Mon, 12 Aug 2024 15:52:11 +0000

Add `rust-version.workspace = true` to all crates (#9112)Right now this is only on some crates such as `wasmtime` itself and`wasmtime-cli`, but by applying it to all crates it helps with versionselection of those using just Cranelift for example. List of files: /wasmtime-44.0.1/crates/test-programs/artifacts/Cargo.toml

00c15df9 - Revert "wasi-adapter: Implement provider crate that embeds the adapter binaries (#8792)" (#8856)

Fri, 21 Jun 2024 14:25:16 +0000

Revert "wasi-adapter: Implement provider crate that embeds the adapter binaries (#8792)" (#8856)* Revert "wasi-adapter: Implement provider crate that embeds the adapter binaries (#8792)"This reverts commit 2dbf8f15b3c07b51d090782d9be7172358799563.* Enable requisite feature for cranelift-frontend testing List of files: /wasmtime-44.0.1/crates/test-programs/artifacts/Cargo.toml

2dbf8f15 - wasi-adapter: Implement provider crate that embeds the adapter binaries (#8792)

Tue, 18 Jun 2024 15:38:05 +0000

wasi-adapter: Implement provider crate that embeds the adapter binaries (#8792)* wasi-adapter: Implement provider crate that embeds the adapter binaries* Upgrade wasi adapters to the latest version* Update adapter docs* Recompile asi adapters with 1.78* Recompile wasi adapters with 1.79* Add some debugging to adapter build script* Fix script debugging* Compute wasi adapter version based on latest adapter commit hash* Try to bless wasi adapters again* Try to work around CI auto-merges* Revert to just using workspace version* Add the wasi adapter provider to the crate publication list* Use wasi adapter provider in artifacts test + explicit MSRV in CI* Explicit adapter crate version* Small fix* Remove version info from adapter metadata* Check but don't install rust toolchain in build script* Bless after rebase---------Co-authored-by: Alex Crichton List of files: /wasmtime-44.0.1/crates/test-programs/artifacts/Cargo.toml

f1411653 - Remove the borrow checking from `wiggle` entirely (#8702)

Fri, 31 May 2024 17:22:23 +0000

Remove the borrow checking from `wiggle` entirely (#8702)* Remove the borrow checking from `wiggle` entirelyThis commit is a refactoring of the `wiggle` crate which powers the`*.witx`-based bindings generation of Wasmtime for wasip1 support.Originally `wiggle` had a full-blown runtime borrow checker whichverified that borrows were disjoint when appropriate. In #8277 this wasremoved in favor of a more coarse "either all shared or all mutable"guarantee. It turns out that this exactly matches what the Rust typesystem guarantees at compile time as well.This commit removes all runtime borrow checking in favor of compile-timeborrow checking instead. This means that there is no longer thepossibility of a runtime error arising from borrowing errors. Currentbindings in Wasmtime needed no restructuring to work with this new API.The source of the refactors here are all in the `wiggle` crate. Changesinclude:* The `GuestPtr` type lost its type parameter. Additionally it only contains a `u32` pointer now instead.* The `GuestMemory` trait is replaced with a simple `enum` of possibilities.* Helper methods on `GuestPtr` are all moved to `GuestMemory`.* A number of abstractions were simplified now that borrow checking is no longer necessary.* Generated trait methods now all take `&mut GuestMemory<'_>` as an argument.These changes were then propagated to the `wasmtime-wasi` and`wasi-common` crates in their preview0 and preview1 implementations ofWASI. All changes are just general refactors, no functional change isintended here.* Review comments* Fix publishing of wiggle-macro crate* Fix wiggle docs List of files: /wasmtime-44.0.1/crates/test-programs/artifacts/Cargo.toml

4a096c8e - Use an incremental cache when testing WASI (#8354)

Fri, 12 Apr 2024 23:11:47 +0000

Use an incremental cache when testing WASI (#8354)Currently we've got a good number of WASI tests and they're allrelatively large. We also can run a single test in up to threeconfigurations:* As-is with a module* As a component in "sync" mode* As a component in "async" modeIn debug mode compilation of all these modules can take a significantchunk of time (20-30s in total for test suites) This commit updatesthese test suites to use an in-memory per-process incremental cachebacked by a simple `Mutex`. This gives some good speedups indebug mode, locally the wasi-common, wasmtime-wasi, andwasmtime-wasi-http test suites were reduced from 32 to 17 seconds. I'dexpect larger speedups on less-parallel machines such as our CI. List of files: /wasmtime-44.0.1/crates/test-programs/artifacts/Cargo.toml

08c7359f - Update a few crates on their major version tracks (#7908)

Mon, 12 Feb 2024 15:56:27 +0000

Update a few crates on their major version tracks (#7908)Found via `cargo outdated` and the vets here were easy enough. List of files: /wasmtime-44.0.1/crates/test-programs/artifacts/Cargo.toml

5856590f - Configure workspace lints, enable running some Clippy lints on CI (#7561)

Mon, 20 Nov 2023 23:23:41 +0000

Configure workspace lints, enable running some Clippy lints on CI (#7561)* Configure Rust lints at the workspace levelThis commit adds necessary configuration knobs to have lints configuredat the workspace level in Wasmtime rather than the crate level. Thisuses a feature of Cargo first released with 1.74.0 (last week) of the`[workspace.lints]` table. This should help create a more consistent setof lints applied across all crates in our workspace in addition topossibly running select clippy lints on CI as well.* Move `unused_extern_crates` to the workspace levelThis commit configures a `deny` lint level for the`unused_extern_crates` lint to the workspace level rather than theprevious configuration at the individual crate level.* Move `trivial_numeric_casts` to workspace level* Change workspace lint levels to `warn`CI will ensure that these don't get checked into the codebase andotherwise provide fewer speed bumps for in-process development.* Move `unstable_features` lint to workspace level* Move `unused_import_braces` lint to workspace level* Start running Clippy on CIThis commit configures our CI to run `cargo clippy --workspace` for allmerged PRs. Historically this hasn't been all the feasible due to theamount of configuration required to control the number of warnings onCI, but with Cargo's new `[lint]` table it's possible to have aone-liner to silence all lints from Clippy by default. This commit bydefault sets the `all` lint in Clippy to `allow` to by-default disablewarnings from Clippy. The goal of this PR is to enable selective accessto Clippy lints for Wasmtime on CI.* Selectively enable `clippy::cast_sign_loss`This would have fixed #7558 so try to head off future issues with thatby warning against this situation in a few crates. This lint is stillquite noisy though for Cranelift for example so it's not worthwhile atthis time to enable it for the whole workspace.* Fix CI errorprtest:full List of files: /wasmtime-44.0.1/crates/test-programs/artifacts/Cargo.toml

f4be3606 - Refactor the test-programs test suite (#7182)

Mon, 09 Oct 2023 19:22:42 +0000

Refactor the test-programs test suite (#7182)* Refactor the test-programs test suiteThis commit is a large refactoring that reorganizes `test-programs` andhow we tests wasms in Wasmtime. Often writing tests requires complicatedinteractions with the guest which can't be done via hand-written `*.wat`syntax and requires a compiler to get engaged. For this purpose Wasmtimecurrently has the `crates/test-programs/*` test suite which builds filesfrom source and then runs the tests. This has been somewhat cumbersomein the past though and it's not been easy to extend this over time, sothis commit attempts to address this.The scheme implemented in this PR looks like:* All wasm test programs live in `crates/test-programs/src/bin/*.rs`. All of them, no exceptions.* Wasm tests have shared support located at `crates/test-programs/src/lib.rs` and its submodules, such as bindings generation for WASI.* Wasm tests are built by a new `crates/test-programs/artifacts` crate. This crate compiles modules and additionally creates components for all test programs. The crate itself only records the path to these outputs and a small amount of testing support, but otherwise doesn't interact with `wasmtime`-the-crate itself.* All tests in `crates/test-programs/tests/*.rs` have moved. For example wasi-http tests now live at `crates/wasi-http/tests/*.rs`. Legacy tests of wasi-common now live at `crates/wasi-common/tests/*.rs`. Modern tests for preview2 live at `crates/wasi/tests/*.rs`.* Wasm tests are bucketed based on their filename prefix. For example `preview1_*` is tested in wasi-common and wasmtime-wasi. The `preview2_*` prefix is only tested with wasmtime-wasi, however.* A new `cli_*` prefix is used to execute tests as part of `tests/all/main.rs`. This is a new submodule in `tests/all/cli_tests.rs` which executes these components on the command line. Many old "command" tests were migrated here.* Helper macros are generated to assert that a test suite is run in its entirety. This way if a `preview1_*` test is added it's asserted to get added to both wasi-common and wasmtime-wasi in the various modes they run tests.Overall this moved a number of tests around and refactored some edges ofthe tests, but this should not lose any tests (except one that wasn'tactually testing anything). Additionally the hope is that it's mucheasier to add tests in the future. The process is to add a new file in`crates/test-programs/src/bin/*.rs` named appropriately. For example apreview2 executable is `preview2_*` and a CLI tests is `cli_*`. Whenbuilding the test suite an error is generated in the appropriate modulethen of "please write a test here", and then a test is written in thesame manner as the other tests in the module.* Remove no-longer-needed fetchesprtest:full* I'm worried wasi is running low on semicolons* Add the WASI target in all CI actions* Add unknown-unknown target on all CI builders too* Fix building test artifacts under miriNeed to avoid wrappers for these cross-compiled targets* Break circular dependency for packagingDon't use the workspace dep for `wasmtime-wasi` since it injects aversion, instead use a `path = '..'` dependency to fool Cargo intodropping the dependency during the package phase.* Fix some merge conflicts with tests* Fix rebase for new tests* Remove stray comment* Fix some flaky tests* Fix network tests in synchronous modeThis commit is an attempt to fix some networking tests in synchronousmode in our test suite. Currently networking tests don't actually run insynchronous mode on CI which is why no failures have been surfaced yet,but the refactoring in #7182 is going to start doing this.Currently the `udp_sample_application.rs` test blocks infinitely insynchronous mode for me locally, most of the time. This appears to be aninteraction between how Tokio handles readiness and how we'reentering the event loop. We're effectively entering the Tokio event loopwith a future that's always ready which ends up starving Tokio ofotherwise performing its background work such as updating flags forreadiness of reading/writing.The fix here is to add a yield at the start of an `in_tokio` block whichis used in synchronous mode. This is a kludge fix but the intention isto enable Tokio to have a chance to update readiness flags and processevents from epoll/kqueue/etc.An additional fix to this issue is WebAssembly/wasi-sockets#64 where thetest is waiting on `READABLE` or `WRITABLE`, but in this specific caseit should only wait on `READABLE`. If it waited on just this then thatwould also fix this issue. Nevertheless having a `yield_now` is expectedto have little-to-no overhead and otherwise fix this edge case of analways-ready future.* Fix passing empty arguments on the CLI* Add another blocking accept* Update crates/test-programs/src/bin/api_proxy.rsCo-authored-by: Trevor Elliott ---------Co-authored-by: Trevor Elliott List of files: /wasmtime-44.0.1/crates/test-programs/artifacts/Cargo.toml