Skip to content
CI

Fix file watcher panic when event has no paths (#14364) #35742

Sign in to view logs

Fix file watcher panic when event has no paths (#14364)

Fix file watcher panic when event has no paths (#14364) #35742

Triggered via push November 16, 2024 07:36
@MichaReiserMichaReiser
pushed a6a3d3f
main
Status Success
Total duration 9m 45s
Artifacts 1

ci.yaml

on: push
Determine changes
9s
Determine changes
cargo fmt
18s
cargo fmt
python package
1m 13s
python package
pre-commit
43s
pre-commit
mkdocs
2m 43s
mkdocs
cargo test (linux)
4m 31s
cargo test (linux)
cargo clippy
1m 55s
cargo clippy
cargo test (windows)
9m 14s
cargo test (windows)
cargo test (wasm)
1m 29s
cargo test (wasm)
cargo build (release)
4m 48s
cargo build (release)
cargo build (msrv)
4m 1s
cargo build (msrv)
cargo fuzz
5m 6s
cargo fuzz
test scripts
1m 8s
test scripts
cargo shear
23s
cargo shear
formatter instabilities and black similarity
4m 21s
formatter instabilities and black similarity
benchmarks
5m 11s
benchmarks
Fuzz the parser
0s
Fuzz the parser
ecosystem
0s
ecosystem
test ruff-lsp
35s
test ruff-lsp
Fit to window
Zoom out
Zoom in

Annotations

2 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/
cargo fuzz
Unexpected input(s) 'tool', valid inputs are ['']

Artifacts

Produced during runtime
Name Size
ruff
84.4 MB