Skip to content

Fix configuration inheritance for configurations specified in the LSP settings #32813

Fix configuration inheritance for configurations specified in the LSP settings

Fix configuration inheritance for configurations specified in the LSP settings #32813

Triggered via pull request September 8, 2024 19:26
Status Success
Total duration 13m 3s
Artifacts 3

ci.yaml

on: pull_request
cargo test (linux)
3m 45s
cargo test (linux)
cargo clippy
1m 39s
cargo clippy
cargo test (windows)
7m 46s
cargo test (windows)
cargo test (wasm)
1m 27s
cargo test (wasm)
cargo build (release)
4m 46s
cargo build (release)
cargo build (msrv)
3m 15s
cargo build (msrv)
cargo fuzz
4m 33s
cargo fuzz
test scripts
55s
test scripts
cargo shear
25s
cargo shear
formatter instabilities and black similarity
0s
formatter instabilities and black similarity
benchmarks
4m 51s
benchmarks
Fuzz the parser
0s
Fuzz the parser
ecosystem
8m 43s
ecosystem
test ruff-lsp
21s
test ruff-lsp
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
cargo test (wasm)
The following actions use a deprecated Node.js version and will be forced to run on node20: jetli/[email protected]. 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 ['']

Artifacts

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