Skip to content

Use binary semantics when __iadd__ et al are unbound #34684

Use binary semantics when __iadd__ et al are unbound

Use binary semantics when __iadd__ et al are unbound #34684

Re-run triggered October 30, 2024 03:02
Status Success
Total duration 9m 13s
Artifacts 3

ci.yaml

on: pull_request
cargo test (linux)
4m 7s
cargo test (linux)
cargo clippy
1m 58s
cargo clippy
cargo test (windows)
9m 3s
cargo test (windows)
cargo test (wasm)
1m 33s
cargo test (wasm)
cargo build (release)
5m 36s
cargo build (release)
cargo build (msrv)
3m 32s
cargo build (msrv)
cargo fuzz
4m 30s
cargo fuzz
test scripts
1m 1s
test scripts
cargo shear
28s
cargo shear
formatter instabilities and black similarity
0s
formatter instabilities and black similarity
benchmarks
4m 29s
benchmarks
Fuzz the parser
0s
Fuzz the parser
ecosystem
9m 3s
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
ecosystem-result
550 Bytes
pr-number
140 Bytes