Skip to content

CI: autotest fails with ENV ISSUE for external PRs (memos_local_plugin environment preparation failed) #2476

Open

Description

@akushonkamen

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 ISSUE

The 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

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

  1. added
    status:needs-triageNeeds initial triage | 需要初步判断 & 问题复现
    types:bugSomething isn't working | 功能异常
    on Oct 8, 2026
  2. akushonkamen commented on Oct 9, 2026

    @akushonkamen
    Author

    Status update and request for CI admin attention — tagging @CarltonXiang @hijzy @whipser030 @syzsunshine219 since this needs someone with CI access.

    The memos_local_plugin ENV 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 at b784e66), 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_plugin scope 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.

  3. akushonkamen commented on Oct 10, 2026

    @akushonkamen
    Author

    Second escalation — ~29 hours since our tagged report, still zero response. Re-tagging @CarltonXiang @hijzy @whipser030 @syzsunshine219 because this needs someone with CI access.

    PR Branch (head) ENV ISSUE runs (UTC, 2026-10-08)
    #2464 fix/plugin-storage-limit-clamp (cd70df6) 13:18:08, 16:43:37
    #2465 fix/bridge-esm-init-logging (5c18da8) 16:05:07
    #2466 fix/skill-verifier-resonance-tool-evidence (b784e66) 16:23:35, 18:06:40, 21:20:28
    #2468 fix/fetch-transient-cause-chain (7803d68) 17:46:47

    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_plugin scope — 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 at b784e66), and local verification is fully green (npm run test:unit — 1594 tests pass, tsc --noEmit clean). The only missing step is a working gate.

    Explicit ask: (a) a CI admin checks and restores the memos_local_plugin scope 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.

  4. github-actions commented on Nov 10, 2026

    @github-actions
    Contributor

    This issue has been automatically marked as stale due to inactivity.

  5. added
    status:staleAuto-marked stale after 30d inactivity; closes 7d later unless exempt.
    on Nov 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

area:pluginOpenClaw & Hermesstatus:needs-triageNeeds initial triage | 需要初步判断 & 问题复现status:staleAuto-marked stale after 30d inactivity; closes 7d later unless exempt.types:bugSomething isn't working | 功能异常

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions