Repository navigation
fix: canon directional literals, terse K: boundary, mcp nl_query config, gpu OOB GROUP BY keys #11687
Annotations
23 errors, 2 warnings, and 8 notices
|
Self-test the ring doorbells fail LOUD on a missing credential (#4966)
ci-summary failed — see the non-passing gating checks above.
|
|
Self-test the ring doorbells fail LOUD on a missing credential (#4966)
ci-summary failed — see the non-passing gating checks above.
|
|
Zero-dispatch watchdog suite (policy + behaviour + YAML seam —
PR #99900001 ref gh-readonly-queue/main/pr-99900001-3cc1bf828c1335577069f5fa65d832c0ae1c8c38: simulated failure for dequeuePullRequest
|
|
Self-test the HEAVY-set drift alarm (drift classes + empty-measurement fail-loud)
cannot read event stream /tmp/tmphadv30uq/gone.jsonl: [Errno 2] No such file or directory: '/tmp/tmphadv30uq/gone.jsonl'
|
|
Self-test the HEAVY-set drift alarm (drift classes + empty-measurement fail-loud)
/tmp/tmphadv30uq/no-heavy.yml: no `HEAVY:` assignment — the load-aware shard matrix's single source of truth is gone, so there is nothing to check drift against
|
|
Self-test the HEAVY-set drift alarm (drift classes + empty-measurement fail-loud)
newly_slow (55.0s): measured heavy but NOT in `HEAVY` — it is running inside a bulk shard right now, re-skewing the load-aware split
|
|
Self-test the CI execution-latency alarm (3 choke modes + YAML seam)
ci execution-latency alarm infrastructure failure: no usable repo slug: 'not-a-slug'
|
|
Self-test the CI execution-latency alarm (3 choke modes + YAML seam)
1 CI execution-latency breach(es) in o/r — runner pickup, cron delivery, or execution time is outside its measured band
|
|
Self-test the CI execution-latency alarm (3 choke modes + YAML seam)
ci execution-latency alarm infrastructure failure: empty M1 scan set: no workflow has a `schedule:` plus a trigger outside ['schedule', 'workflow_dispatch'] — either the repo changed shape or the scope predicate broke. Refusing to report health over an empty population.
|
|
Self-test the CI execution-latency alarm (3 choke modes + YAML seam)
ci execution-latency alarm infrastructure failure: empty scan set: no workflows discovered
|
|
Self-test the alarm/detector lanes are DECLARED non-gating (sq-huwr8)
ci-summary failed — see the non-passing gating checks above.
|
|
Self-test the alarm/detector lanes are DECLARED non-gating (sq-huwr8)
ci-summary failed — see the non-passing gating checks above.
|
|
Self-test the review-lane blind-spot alarm (verdict obligations + YAML seam)
review-lane alarm infrastructure failure: repo must be OWNER/REPOSITORY (set --repo or GITHUB_REPOSITORY)
|
|
Self-test the review-lane blind-spot alarm (verdict obligations + YAML seam)
review-lane alarm infrastructure failure: repo must be OWNER/REPOSITORY (set --repo or GITHUB_REPOSITORY)
|
|
Self-test the review-lane blind-spot alarm (verdict obligations + YAML seam)
1 open PR(s) have no countable review verdict and are unreachable by every review producer — verdict PRODUCTION, not transport, is the stalled stage
|
|
Self-test the review-lane blind-spot alarm (verdict obligations + YAML seam)
1 open PR(s) have no countable review verdict and are unreachable by every review producer — verdict PRODUCTION, not transport, is the stalled stage
|
|
Self-test the review-lane blind-spot alarm (verdict obligations + YAML seam)
1 open PR(s) have no countable review verdict and are unreachable by every review producer — verdict PRODUCTION, not transport, is the stalled stage
|
|
Self-test the review-lane blind-spot alarm (verdict obligations + YAML seam)
1 open PR(s) have no countable review verdict and are unreachable by every review producer — verdict PRODUCTION, not transport, is the stalled stage
|
|
Self-test the nightly selection-bug alarm (correlation + fail-loud — sq-va7at)
selection-alarm infrastructure error: gather_failed_jobs: empty failed-job set on a conclusion-unknown-concluded run (run_id=1); jobs-API shape surprise or filter=latest re-run race — cannot correlate, refusing to exit 0
|
|
Self-test the nightly selection-bug alarm (correlation + fail-loud — sq-va7at)
selection-alarm infrastructure error: gather_failed_jobs: empty failed-job set on a timed_out-concluded run (run_id=1); jobs-API shape surprise or filter=latest re-run race — cannot correlate, refusing to exit 0
|
|
Self-test the nightly selection-bug alarm (correlation + fail-loud — sq-va7at)
ffffffffffff: simulated git diff failure
|
|
Self-test Miri verdict classifier (timeout-vs-UB split + exit codes)
the libtest-json-plus stream carried no ok/failed/timeout events — nextest likely failed to build/run the shard (see the .stderr above). Failing the shard: an empty verdict is NOT a clean pass.
|
|
Self-test Miri verdict classifier (timeout-vs-UB split + exit codes)
a::aliasing_ub failed under Miri (not a timeout) — a genuine undefined-behaviour / assertion finding.
|
|
Self-test Miri verdict classifier (timeout-vs-UB split + exit codes)
a::heavy_loader exceeded the per-test cap — known cost debt tracked by sq-0s15k (non-fatal).
|
|
Self-test Miri verdict classifier (timeout-vs-UB split + exit codes)
a::heavy_loader exceeded the per-test cap — known cost debt tracked by sq-0s15k (non-fatal).
|
|
Self-test the CI execution-latency alarm (3 choke modes + YAML seam)
CI execution latency is within every measured threshold
|
|
Self-test the review-lane blind-spot alarm (verdict obligations + YAML seam)
no PR is outside every review producer's reach
|
|
Self-test the review-lane blind-spot alarm (verdict obligations + YAML seam)
no PR is outside every review producer's reach
|
|
Self-test the review-lane blind-spot alarm (verdict obligations + YAML seam)
no PR is outside every review producer's reach
|
|
Self-test the review-lane blind-spot alarm (verdict obligations + YAML seam)
no PR is outside every review producer's reach
|
|
Self-test ci-summary gate loop (verdict semantics + adaptive saturation budget — sq-90cv4)
ci-summary #3505: newest workflow 'CI' run 104 was cancelled; requested its one bounded re-run (run_attempt marker=1).
|
|
|
|
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
|
background
wait
wait-all
cancel
parallel
Loading