Allow cranelift and satellite crates to be able to build in full no-std mode #39316
stevefan1999-personalmain.yml
on: pull_request
Determine CI jobs to run
16s
Matrix: micro_checks
Rustfmt
32s
Check JS
9s
Clang format
20s
Clippy
3m 54s
MSRV check
3m 41s
Monolith Checks
1m 9s
Matrix: build
Matrix: Miri
Matrix: platform_checks
Matrix: test
Matrix: test_capi
Matrix: test_wasi_nn
Matrix: Test wasi-tls
Cargo deny
31s
Doc build
One-off special tests
Nightly tests
2m 25s
GC Zeal Tests
Test wasmtime-fuzzing
Test DWARF debugging
3m 53s
Test the min-platform example
Run benchmarks
Meta deterministic check
verify-publish
Test guest debugging
1m 51s
Cargo vet failed on a Pull Request
push-tag
0s
File an issue if this build failed and was cron-triggered
0s
Annotations
22 errors and 8 warnings
|
Cargo vet
Process completed with exit code 255.
|
|
Cargo vet
Process completed with exit code 255.
|
|
Monolith Checks
Process completed with exit code 101.
|
|
Check wasmtime-bench-api
Process completed with exit code 123.
|
|
Test Linux x86_64 (wasmtime-wasi)
Process completed with exit code 101.
|
|
Check wasmtime-wizer
Process completed with exit code 123.
|
|
Test Linux x86_64 (wasmtime)
Process completed with exit code 101.
|
|
Test guest debugging
Process completed with exit code 101.
|
|
Test Linux x86_64 (wasmtime-cli-wast)
Process completed with exit code 101.
|
|
Test Linux x86_64 (wasmtime-cli-all)
Process completed with exit code 101.
|
|
Test Linux x86_64 (wasmtime-cli-other)
Process completed with exit code 101.
|
|
Check wasmtime-wasi-http
Process completed with exit code 123.
|
|
Nightly tests
Process completed with exit code 101.
|
|
MSRV check
Process completed with exit code 101.
|
|
Clippy
Process completed with exit code 101.
|
|
Test Linux x86_64 (2/8)
Process completed with exit code 101.
|
|
Test DWARF debugging
Process completed with exit code 101.
|
|
Test Linux x86_64 (3/8)
Process completed with exit code 101.
|
|
Test Linux x86_64 (1/8)
Process completed with exit code 101.
|
|
Check wasmtime-cli
Process completed with exit code 123.
|
|
Check wasmtime
Process completed with exit code 123.
|
|
Record the result of testing and building steps
Process completed with exit code 1.
|
|
Test Linux x86_64 (wasmtime-wasi)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test Linux x86_64 (wasmtime)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test Linux x86_64 (wasmtime-cli-wast)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test Linux x86_64 (wasmtime-cli-all)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test Linux x86_64 (wasmtime-cli-other)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test Linux x86_64 (2/8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test Linux x86_64 (3/8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test Linux x86_64 (1/8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|