Skip to content
CI

[red-knot] Handle possibly-unbound instance members #41172

Sign in to view logs

[red-knot] Handle possibly-unbound instance members

[red-knot] Handle possibly-unbound instance members #41172

Triggered via pull request February 25, 2025 18:39
@sharkdpsharkdp
synchronize #16363
david/possibly-unbound-instance-members
Status Success
Total duration 5m 45s
Billable time 4m
Artifacts 2

ci.yaml

on: pull_request
Determine changes
13s
Determine changes
cargo fmt
23s
cargo fmt
cargo build (release)
0s
cargo build (release)
python package
1m 17s
python package
pre-commit
3m 14s
pre-commit
mkdocs
2m 30s
mkdocs
cargo test (linux)
2m 2s
cargo test (linux)
cargo clippy
1m 54s
cargo clippy
cargo test (linux, release)
4m 34s
cargo test (linux, release)
cargo test (windows)
3m 39s
cargo test (windows)
cargo test (wasm)
1m 44s
cargo test (wasm)
cargo build (msrv)
2m 4s
cargo build (msrv)
cargo fuzz build
4m 11s
cargo fuzz build
test scripts
1m 10s
test scripts
cargo shear
23s
cargo shear
formatter instabilities and black similarity
0s
formatter instabilities and black similarity
benchmarks
4m 15s
benchmarks
fuzz parser
0s
fuzz parser
ecosystem
20s
ecosystem
test ruff-lsp
34s
test ruff-lsp
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
ecosystem
No files were found with the provided path: ecosystem-result. No artifacts will be uploaded.
cargo fuzz build
Unexpected input(s) 'tool', valid inputs are ['']

Artifacts

Produced during runtime
Name Size
pr-number
140 Bytes
ruff
87.8 MB