Skip to content

Consider VS Code cell metadata to determine valid code cells #31835

Consider VS Code cell metadata to determine valid code cells

Consider VS Code cell metadata to determine valid code cells #31835

Triggered via pull request August 13, 2024 16:32
Status Success
Total duration 13m 18s
Artifacts 3

ci.yaml

on: pull_request
cargo test (linux)
4m 2s
cargo test (linux)
cargo clippy
1m 45s
cargo clippy
cargo test (windows)
7m 45s
cargo test (windows)
cargo test (wasm)
1m 31s
cargo test (wasm)
cargo build (release)
4m 36s
cargo build (release)
cargo build (msrv)
3m 9s
cargo build (msrv)
cargo fuzz
4m 58s
cargo fuzz
test scripts
1m 1s
test scripts
cargo shear
23s
cargo shear
formatter instabilities and black similarity
0s
formatter instabilities and black similarity
benchmarks
4m 56s
benchmarks
Fuzz the parser
0s
Fuzz the parser
ecosystem
8m 39s
ecosystem
test ruff-lsp
20s
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
72.6 MB