Skip to content

[red-knot] Use vendored typeshed stubs for stdlib module resolution #30391

[red-knot] Use vendored typeshed stubs for stdlib module resolution

[red-knot] Use vendored typeshed stubs for stdlib module resolution #30391

Triggered via pull request July 9, 2024 09:17
Status Success
Total duration 12m 53s
Artifacts 3

ci.yaml

on: pull_request
cargo test (linux)
3m 36s
cargo test (linux)
cargo clippy
1m 51s
cargo clippy
cargo test (windows)
7m 2s
cargo test (windows)
cargo test (wasm)
1m 15s
cargo test (wasm)
cargo build (release)
5m 1s
cargo build (release)
cargo build (msrv)
3m 7s
cargo build (msrv)
cargo fuzz
4m 56s
cargo fuzz
test scripts
1m 11s
test scripts
cargo shear
24s
cargo shear
formatter instabilities and black similarity
0s
formatter instabilities and black similarity
benchmarks
5m 25s
benchmarks
Fuzz the parser
0s
Fuzz the parser
ecosystem
8m 42s
ecosystem
test ruff-lsp
20s
test ruff-lsp
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
cargo test (wasm)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: jetli/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
mkdocs
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
cargo fuzz
Unexpected input(s) 'tool', valid inputs are ['']

Artifacts

Produced during runtime
Name Size
ecosystem-result Expired
226 Bytes
pr-number Expired
140 Bytes
ruff Expired
73 MB