Skip to content
CI

[red-knot] detect invalid return type #41872

Sign in to view logs

[red-knot] detect invalid return type

[red-knot] detect invalid return type #41872

Triggered via pull request March 12, 2025 01:32
@carljmcarljm
synchronize #16540
mtshiba:16248-return-type-checking
Status Success
Total duration 5m 39s
Billable time 6m
Artifacts 2

ci.yaml

on: pull_request
Determine changes
12s
Determine changes
cargo fmt
22s
cargo fmt
cargo build (release)
0s
cargo build (release)
python package
1m 19s
python package
pre-commit
3m 24s
pre-commit
mkdocs
2m 34s
mkdocs
cargo test (linux)
2m 30s
cargo test (linux)
cargo clippy
1m 53s
cargo clippy
cargo test (linux, release)
4m 10s
cargo test (linux, release)
cargo test (windows)
5m 7s
cargo test (windows)
cargo test (wasm)
1m 40s
cargo test (wasm)
cargo build (msrv)
2m 11s
cargo build (msrv)
cargo fuzz build
5m 4s
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 18s
benchmarks
fuzz parser
0s
fuzz parser
ecosystem
19s
ecosystem
test ruff-lsp
35s
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
88.2 MB