Skip to content

test(ci): keep isolated CLI checks offline - #97

Merged
pacphi merged 2 commits into
mainfrom
codex/fix-ci-drift-cache
Jul 30, 2026
Merged

pacphi merged 2 commits into
mainfrom
codex/fix-ci-drift-cache

Conversation

@pacphi

@pacphi pacphi commented Jul 30, 2026

Copy link
Copy Markdown
Owner

Outcome

Eliminates accidental npm egress from the provider CLI integration sandbox and the cross-platform CLI smoke job while preserving production version-drift behavior unchanged.

Root cause

The CLI drift nudge predates these tests. Fresh test homes had no versionCheck cache, so each spawned provider command ran two sequential npm view probes. On Windows runners both reached their 20-second timeout, making each test take about 40.5 seconds. The smoke status path additionally paid four probes. Node buffered the next test file, making all Windows lanes appear hung at the same prior output line.

Change

  • seed the provider integration sandbox with a fresh, empty, truthful drift result
  • seed the CLI smoke HOME with both package and self-drift cache entries
  • set XDG_CONFIG_HOME explicitly for POSIX smoke parity
  • leave all production drift/nudge code and upgrade semantics untouched

Evidence

  • affected provider file: 14/14 pass in 4.8s locally
  • previous Windows log: affected tests ~40.5s each; unit step 590.8s
  • pnpm run check
  • pnpm audit --audit-level high
  • pnpm run lint:links:internal
  • workflow YAML parse
  • ak x verify memory passes; project AgentDB checkpoint confirmed in the ADR-0016 native sibling store

@pacphi
pacphi merged commit c2e2bc1 into main Jul 30, 2026
11 checks passed
@pacphi
pacphi deleted the codex/fix-ci-drift-cache branch July 30, 2026 22:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant