Skip to content
CI

Use a derive macro for Violations #36193

Sign in to view logs

Use a derive macro for Violations

Use a derive macro for Violations #36193

Triggered via pull request November 23, 2024 16:55
@MichaReiserMichaReiser
synchronize #14557
micha/violation-derive-macro
Status Success
Total duration 7m 32s
Billable time 6m
Artifacts 3

ci.yaml

on: pull_request
Determine changes
10s
Determine changes
cargo fmt
20s
cargo fmt
python package
1m 16s
python package
pre-commit
33s
pre-commit
mkdocs
2m 43s
mkdocs
cargo test (linux)
1m 41s
cargo test (linux)
cargo clippy
1m 53s
cargo clippy
cargo test (windows)
5m 58s
cargo test (windows)
cargo test (wasm)
1m 29s
cargo test (wasm)
cargo build (release)
0s
cargo build (release)
cargo build (msrv)
4m 6s
cargo build (msrv)
cargo fuzz build
0s
cargo fuzz build
test scripts
1m 0s
test scripts
cargo shear
22s
cargo shear
formatter instabilities and black similarity
3m 20s
formatter instabilities and black similarity
benchmarks
5m 0s
benchmarks
fuzz parser
0s
fuzz parser
ecosystem
3m 49s
ecosystem
test ruff-lsp
35s
test ruff-lsp
Fit to window
Zoom out
Zoom in

Annotations

1 warning
cargo test (wasm)
The following actions use a deprecated Node.js version 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/

Artifacts

Produced during runtime
Name Size
ecosystem-result
245 Bytes
pr-number
140 Bytes
ruff
85.4 MB