Skip to content

fix: make five upstream-parity resolution rules stricter or more exact #679

fix: make five upstream-parity resolution rules stricter or more exact

fix: make five upstream-parity resolution rules stricter or more exact #679

Triggered via pull request October 1, 2026 22:54
Status Cancelled
Total duration 13m 2s
Artifacts –

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 5 notices
Windows Tests
Canceling since a higher priority waiting request for CI-refs/pull/295/merge exists
CI Success
Process completed with exit code 1.
CI gate
required job 'windows-test' concluded 'cancelled', not 'success'
CI
Canceling since a higher priority waiting request for CI-refs/pull/295/merge exists
sccache stats - macos-watcher
100% - 204 hits, 0 misses, 0 errors
macOS Watcher
Due to capacity constraints, jobs targeting macOS arm64 runners may experience longer queue times.
sccache stats - windows-clippy
93% - 293 hits, 23 misses, 0 errors
sccache stats - linux
99% - 1806 hits, 15 misses, 0 errors
sccache stats - windows-test
89% - 288 hits, 35 misses, 0 errors