Repository navigation
Description
Summary
Since ~13:18 UTC today (2026-10-08), every autotest run on our currently-open external PRs fails at environment preparation with:
Environment preparation failed before any gating tests executed. Failed scopes: memos_local_plugin
The failure is identical across four independent PRs and across re-runs, and no gating test ever executes — so these are CI environment failures, not code failures. We believe the memos_local_plugin scope environment is unhealthy and needs a CI admin look.
Failure timeline (all 2026-10-08 UTC)
| PR | Branch (head) | First ENV ISSUE | Re-run | Result |
|---|---|---|---|---|
| #2464 | fix/plugin-storage-limit-clamp (cd70df6) |
13:18 | 16:43 (same head) | ENV ISSUE both times |
| #2465 | fix/bridge-esm-init-logging (5c18da8) |
16:05 | — | ENV ISSUE |
| #2466 | fix/skill-verifier-resonance-tool-evidence (5af69df → b784e66) |
16:23 | 18:06 (~40 min after first heads-up) | ENV ISSUE both times |
| #2468 | fix/fetch-transient-cause-chain (7803d68) |
17:46 | — | ENV ISSUE |
Sample report (identical wording on all four runs):
⚠️ Automated Test Results: ENV ISSUEThe test environment encountered an issue that requires manual attention.
Details: Environment preparation failed before any gating tests executed. Failed scopes: memos_local_plugin
What we have ruled out
- Not transient: failures span ~5 hours (13:18 → 18:06), and re-runs on both unchanged and updated heads fail the same way (fix(plugin): stop clamping storage list queries to 500 rows #2464 at 16:43, fix(plugin): let skill resonance see tool sub-step evidence #2466 at 18:06).
- Not PR-specific: four independent branches touching different parts of the plugin all fail identically at the same scope.
- Not the code: gating tests never start. For reference, on the fix(plugin): let skill resonance see tool sub-step evidence #2466 head a local verification passes cleanly:
npm run test:unit→ 181 files / 1594 tests pass,tsc --noEmitclean.
Request
Could a CI admin please check the memos_local_plugin scope environment preparation step (provisioning, cache, credentials, or whatever the scope bootstrap depends on), and once it is healthy manually trigger a rerun on #2464, #2465, #2466 and #2468? Happy to help debug the scope setup or provide any extra logs from our side.
Activity
akushonkamen commentedon Oct 9, 2026
Status update and request for CI admin attention — tagging @CarltonXiang @hijzy @whipser030 @syzsunshine219 since this needs someone with CI access.
The
memos_local_pluginENV ISSUE is still ongoing: first failure 13:18 UTC, latest re-run 21:20 UTC (~8 hours), now spanning all four open external PRs (#2464, #2465, #2466, #2468). Every run and every re-run fails identically at environment preparation — "Environment preparation failed before any gating tests executed. Failed scopes: memos_local_plugin" — and no gating test has executed at all in that window, so the red statuses do not reflect any branch's code.On the code side, everything is handled: OCR feedback has been fully addressed on the affected branches (#2464 at
cd70df6, #2466 atb784e66), and local verification passes, so we can rule out the PR code as the cause — this is a shared, persistent problem with the scope environment itself.Request: could someone with CI admin access please check the
memos_local_pluginscope environment preparation step (provisioning, cache, credentials), and once it is healthy manually trigger reruns on #2464, #2465, #2466 and #2468? Happy to help debug the scope setup or provide any extra logs from our side.akushonkamen commentedon Oct 10, 2026
Second escalation — ~29 hours since our tagged report, still zero response. Re-tagging @CarltonXiang @hijzy @whipser030 @syzsunshine219 because this needs someone with CI access.
fix/plugin-storage-limit-clamp(cd70df6)fix/bridge-esm-init-logging(5c18da8)fix/skill-verifier-resonance-tool-evidence(b784e66)fix/fetch-transient-cause-chain(7803d68)The numbers: the outage has now run >41 hours (13:18 UTC Oct 8 → 06:40 UTC Oct 10). All four PRs, every run and every re-run, fail at the exact same step — environment preparation of the
memos_local_pluginscope — and no gating test has ever started, so these red statuses say nothing about any branch's code. The bot has not reported anything since 21:20 UTC Oct 8 (~33 hours of total silence). Precedent shows this is fixable fast when someone attends: the ENV ISSUE on external PR #2353 (Sep 9) was cleared within ~1 hour and merged.On the code side nothing is blocking: all OCR feedback is addressed on every affected branch (#2464 at
cd70df6, #2466 atb784e66), and local verification is fully green (npm run test:unit— 1594 tests pass,tsc --noEmitclean). The only missing step is a working gate.Explicit ask: (a) a CI admin checks and restores the
memos_local_pluginscope environment preparation, then manually triggers reruns on #2464, #2465, #2466 and #2468 — or (b) someone points us to the correct channel for CI incidents. The README lists a Discord and a WeChat group — we're also happy to raise this on Discord if that's faster; a pointer to the right channel/owner is welcome.github-actions commentedon Nov 10, 2026
This issue has been automatically marked as stale due to inactivity.