Skip to content
CI

[red-knot] Re-enable linter corpus tests #36670

Sign in to view logs

[red-knot] Re-enable linter corpus tests

[red-knot] Re-enable linter corpus tests #36670

Triggered via pull request December 2, 2024 15:55
@sharkdpsharkdp
opened #14736
david/reenable-linter-corpus-tests
Status Failure
Total duration 5m 27s
Billable time 5m
Artifacts –

ci.yaml

on: pull_request
Determine changes
8s
Determine changes
cargo fmt
25s
cargo fmt
cargo build (release)
0s
cargo build (release)
python package
1m 18s
python package
pre-commit
53s
pre-commit
mkdocs
2m 39s
mkdocs
cargo test (linux)
1m 10s
cargo test (linux)
cargo clippy
1m 48s
cargo clippy
cargo test (linux, release)
3m 10s
cargo test (linux, release)
cargo test (windows)
4m 4s
cargo test (windows)
cargo test (wasm)
1m 41s
cargo test (wasm)
cargo build (msrv)
3m 19s
cargo build (msrv)
cargo fuzz build
0s
cargo fuzz build
test scripts
1m 4s
test scripts
cargo shear
26s
cargo shear
formatter instabilities and black similarity
0s
formatter instabilities and black similarity
benchmarks
4m 56s
benchmarks
fuzz parser
0s
fuzz parser
ecosystem
0s
ecosystem
test ruff-lsp
0s
test ruff-lsp
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 1 warning
cargo test (linux)
Process completed with exit code 1.
cargo build (msrv)
Process completed with exit code 1.
cargo test (linux, release)
Process completed with exit code 1.
cargo test (windows)
Process completed with exit code 100.
cargo fmt
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636