Skip to content

Use binary semantics when __iadd__ et al are unbound #34681

Use binary semantics when __iadd__ et al are unbound

Use binary semantics when __iadd__ et al are unbound #34681

Triggered via pull request October 30, 2024 02:39
Status Cancelled
Total duration 6m 22s
Artifacts

ci.yaml

on: pull_request
cargo test (linux)
3m 23s
cargo test (linux)
cargo clippy
1m 53s
cargo clippy
cargo test (windows)
5m 50s
cargo test (windows)
cargo test (wasm)
1m 42s
cargo test (wasm)
cargo build (release)
4m 45s
cargo build (release)
cargo build (msrv)
3m 4s
cargo build (msrv)
cargo fuzz
4m 40s
cargo fuzz
test scripts
1m 14s
test scripts
cargo shear
23s
cargo shear
formatter instabilities and black similarity
0s
formatter instabilities and black similarity
benchmarks
4m 42s
benchmarks
Fuzz the parser
0s
Fuzz the parser
ecosystem
0s
ecosystem
test ruff-lsp
0s
test ruff-lsp
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 2 warnings
cargo build (msrv)
Process completed with exit code 1.
cargo test (linux)
Process completed with exit code 1.
cargo test (windows)
Canceling since a higher priority waiting request for 'CI-13987/merge-13987' exists
cargo test (windows)
The operation was canceled.
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 ['']