Skip to content

[red-knot] Use Unknown rather than Unbound for unresolved imports #32003

[red-knot] Use Unknown rather than Unbound for unresolved imports

[red-knot] Use Unknown rather than Unbound for unresolved imports #32003

Triggered via pull request August 16, 2024 18:31
Status Success
Total duration 13m 32s
Artifacts 3

ci.yaml

on: pull_request
cargo test (linux)
3m 57s
cargo test (linux)
cargo clippy
1m 51s
cargo clippy
cargo test (windows)
7m 53s
cargo test (windows)
cargo test (wasm)
1m 24s
cargo test (wasm)
cargo build (release)
5m 10s
cargo build (release)
cargo build (msrv)
3m 16s
cargo build (msrv)
cargo fuzz
5m 6s
cargo fuzz
test scripts
54s
test scripts
cargo shear
21s
cargo shear
formatter instabilities and black similarity
0s
formatter instabilities and black similarity
benchmarks
4m 40s
benchmarks
Fuzz the parser
0s
Fuzz the parser
ecosystem
8m 51s
ecosystem
test ruff-lsp
13s
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/[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
72.8 MB