Skip to content

[red-knot] Improve the accuracy of the unresolved-import check #32398

[red-knot] Improve the accuracy of the unresolved-import check

[red-knot] Improve the accuracy of the unresolved-import check #32398

Triggered via pull request August 27, 2024 13:01
Status Success
Total duration 13m 47s
Artifacts 3

ci.yaml

on: pull_request
cargo test (linux)
3m 45s
cargo test (linux)
cargo clippy
1m 46s
cargo clippy
cargo test (windows)
7m 51s
cargo test (windows)
cargo test (wasm)
1m 28s
cargo test (wasm)
cargo build (release)
6m 14s
cargo build (release)
cargo build (msrv)
3m 25s
cargo build (msrv)
cargo fuzz
5m 13s
cargo fuzz
test scripts
58s
test scripts
cargo shear
22s
cargo shear
formatter instabilities and black similarity
0s
formatter instabilities and black similarity
benchmarks
4m 56s
benchmarks
Fuzz the parser
0s
Fuzz the parser
ecosystem
8m 59s
ecosystem
test ruff-lsp
14s
test ruff-lsp
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
cargo test (wasm)
The following actions use a deprecated Node.js version and will be forced to run on node20: jetli/wasm-pack-action@v0.4.0. 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
72.8 MB