Extract import analysis into ruff_python_imports
#69874
ci.yaml
on: pull_request
Determine changes
18s
cargo clippy
1m 40s
cargo test (linux)
4m 0s
cargo test (wasm)
39s
cargo build (msrv)
1m 52s
test scripts
1m 5s
cargo test (linux, release)
3m 5s
cargo fuzz build
4m 58s
fuzz parser
7m 43s
ecosystem
4m 53s
Fuzz for new ty panics
2m 51s
cargo shear
22s
ty completion evaluation
1m 31s
formatter instabilities and black similarity
3m 1s
test ruff-lsp
2m 58s
check playground
0s
benchmarks instrumented (ruff)
3m 25s
Matrix: cargo-test-other
Matrix: benchmarks-instrumented-ty-run
Matrix: benchmarks-walltime-run
all required checks passed
3s
Annotations
3 errors and 2 warnings
|
cargo test (wasm)
Process completed with exit code 1.
|
|
cargo clippy
Process completed with exit code 101.
|
|
all required checks passed
Process completed with exit code 1.
|
|
cargo test (wasm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jetli/wasm-pack-action@0d096b08b4e5a7de8c28de67e11e945404e9eefa. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
cargo build (msrv)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SebRollen/toml-action@b1b3628f55fc3a28208d4203ada8b737e9687876. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
benchmarks-instrumented-ty-binary
Expired
|
82 MB |
sha256:c334daa9594e3e6c5c3565c03634f73cea4d50e5a5d2a2c3f5f2df486f841433
|
|
|
benchmarks-walltime-binary
Expired
|
76 MB |
sha256:a10b76b59784794c2f827f04d635855f7691237e5d96649e58e6de1afcd39485
|
|
|
ecosystem-result
|
245 Bytes |
sha256:ffb5533f0148a6a998b40546c603886ea05487865f62e4826fd8bf5fd65c6c1f
|
|