Skip to content
CI

[red-knot] Use ternary decision diagrams (TDDs) for visibility constraints #39786

Sign in to view logs

[red-knot] Use ternary decision diagrams (TDDs) for visibility constraints

[red-knot] Use ternary decision diagrams (TDDs) for visibility constraints #39786

Triggered via pull request January 31, 2025 22:50
@dcreagerdcreager
synchronize #15861
dcreager/tdd
Status Failure
Total duration 7m 0s
Billable time 5m
Artifacts –

ci.yaml

on: pull_request
Determine changes
13s
Determine changes
cargo fmt
17s
cargo fmt
cargo build (release)
0s
cargo build (release)
python package
1m 16s
python package
pre-commit
3m 22s
pre-commit
mkdocs
2m 25s
mkdocs
cargo test (linux)
1m 56s
cargo test (linux)
cargo clippy
1m 55s
cargo clippy
cargo test (linux, release)
5m 46s
cargo test (linux, release)
cargo test (windows)
4m 48s
cargo test (windows)
cargo test (wasm)
1m 46s
cargo test (wasm)
cargo build (msrv)
4m 45s
cargo build (msrv)
cargo fuzz build
4m 29s
cargo fuzz build
test scripts
1m 7s
test scripts
cargo shear
23s
cargo shear
formatter instabilities and black similarity
3m 15s
formatter instabilities and black similarity
benchmarks
5m 6s
benchmarks
fuzz parser
0s
fuzz parser
ecosystem
0s
ecosystem
test ruff-lsp
0s
test ruff-lsp
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
cargo test (linux)
Process completed with exit code 101.
cargo fuzz build
Unexpected input(s) 'tool', valid inputs are ['']