Skip to content
CI

Use binary semantics when __iadd__ et al are unbound (#13987) #34708

Sign in to view logs

Use binary semantics when __iadd__ et al are unbound (#13987)

Use binary semantics when __iadd__ et al are unbound (#13987) #34708

Triggered via push October 30, 2024 13:09
@charliermarshcharliermarsh
pushed 262c04f
main
Status Success
Total duration 7m 32s
Artifacts 1

ci.yaml

on: push
Determine changes
8s
Determine changes
cargo fmt
18s
cargo fmt
python package
1m 13s
python package
pre-commit
35s
pre-commit
mkdocs
2m 41s
mkdocs
cargo test (linux)
4m 3s
cargo test (linux)
cargo clippy
1m 53s
cargo clippy
cargo test (windows)
7m 3s
cargo test (windows)
cargo test (wasm)
1m 29s
cargo test (wasm)
cargo build (release)
5m 33s
cargo build (release)
cargo build (msrv)
3m 31s
cargo build (msrv)
cargo fuzz
4m 32s
cargo fuzz
test scripts
1m 6s
test scripts
cargo shear
23s
cargo shear
formatter instabilities and black similarity
4m 13s
formatter instabilities and black similarity
benchmarks
4m 33s
benchmarks
Fuzz the parser
0s
Fuzz the parser
ecosystem
0s
ecosystem
test ruff-lsp
24s
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
81.6 MB