Skip to content

[red-knot] Add support for editable installs to the module resolver #30525

[red-knot] Add support for editable installs to the module resolver

[red-knot] Add support for editable installs to the module resolver #30525

Triggered via pull request July 13, 2024 14:44
Status Failure
Total duration 7m 21s
Artifacts

ci.yaml

on: pull_request
cargo test (linux)
2m 36s
cargo test (linux)
cargo clippy
1m 36s
cargo clippy
cargo test (windows)
6m 52s
cargo test (windows)
cargo test (wasm)
1m 5s
cargo test (wasm)
cargo build (release)
4m 5s
cargo build (release)
cargo build (msrv)
2m 28s
cargo build (msrv)
cargo fuzz
4m 49s
cargo fuzz
test scripts
41s
test scripts
cargo shear
20s
cargo shear
formatter instabilities and black similarity
4m 2s
formatter instabilities and black similarity
benchmarks
4m 34s
benchmarks
Fuzz the parser
0s
Fuzz the parser
ecosystem
0s
ecosystem
test ruff-lsp
0s
test ruff-lsp
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 3 warnings
cargo fmt
Process completed with exit code 1.
test scripts
Process completed with exit code 1.
cargo build (msrv)
Process completed with exit code 1.
cargo test (linux)
Process completed with exit code 1.
cargo test (windows)
Process completed with exit code 100.
cargo test (wasm)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: jetli/wasm-pack-action@v0.4.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
mkdocs
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
cargo fuzz
Unexpected input(s) 'tool', valid inputs are ['']