Skip to content
CI

[red-knot] detect invalid return type #41696

Sign in to view logs

[red-knot] detect invalid return type

[red-knot] detect invalid return type #41696

Triggered via pull request March 8, 2025 19:17
@mtshibamtshiba
synchronize #16540
mtshiba:16248-return-type-checking
Status Success
Total duration 6m 10s
Billable time 4m
Artifacts 3

ci.yaml

on: pull_request
Determine changes
10s
Determine changes
cargo fmt
18s
cargo fmt
cargo build (release)
0s
cargo build (release)
python package
1m 28s
python package
pre-commit
3m 29s
pre-commit
mkdocs
2m 23s
mkdocs
cargo test (linux)
2m 0s
cargo test (linux)
cargo clippy
1m 56s
cargo clippy
cargo test (linux, release)
4m 41s
cargo test (linux, release)
cargo test (windows)
3m 47s
cargo test (windows)
cargo test (wasm)
1m 35s
cargo test (wasm)
cargo build (msrv)
2m 2s
cargo build (msrv)
cargo fuzz build
4m 8s
cargo fuzz build
test scripts
1m 3s
test scripts
cargo shear
24s
cargo shear
formatter instabilities and black similarity
0s
formatter instabilities and black similarity
benchmarks
4m 16s
benchmarks
fuzz parser
0s
fuzz parser
ecosystem
2m 44s
ecosystem
test ruff-lsp
32s
test ruff-lsp
Fit to window
Zoom out
Zoom in

Annotations

1 warning
cargo fuzz build
Unexpected input(s) 'tool', valid inputs are ['']

Artifacts

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