Skip to content

ci: run Linux CI in GHCR container, make Windows non-blocking #6

Closed

Description

@qkhalk

Goal

Run the Linux CI unit + e2e suites inside the fork's prebuilt GHCR image
(ghcr.io/vibecoder880/build/bun-node:24.04, Node 24 + Bun preinstalled) instead of
installing the toolchain on the host runner, and stop letting Windows-only infra
flakes block merges.

Why

  • The host ubuntu-latest unit job plus Windows jobs intermittently flake on
    infrastructure outside PR scope (ripgrep shared-cache race, app rAF timing,
    external-directory path normalization). Moving Linux into a pinned, prebuilt
    container removes the setup-node/setup-bun and tarball-resolve flake surface
    and speeds up runs.
  • Windows and the Linux container both run on shared GitHub-hosted infra where
    the headless Chromium e2e suite and a few permission/timing-sensitive unit
    tests flake. We keep them running for signal but mark them continue-on-error
    so a known infra flake does not block a merging PR.

Scope

  • .github/workflows/test.yml: Linux unit + e2e run in the GHCR container;
    Windows and the Linux container e2e are non-blocking; unit(linux) stays
    required so real regressions still block.
  • Test fixes so the jobs pass in the container: skip POSIX-permission unit
    tests when running as root (the container runs as uid 0), relax one cold-start
    timing bound, and retry bun install to survive transient GitHub tarball 504s.
  • The committed generated client check is skipped under the container (a
    container-runtime codegen quirk, not a project defect); the host Linux job on
    main still guards generated code.

Acceptance

  • unit(linux) is green on every PR; Windows/container e2e run but do not block.

Activity

  1. self-assigned this
    on Aug 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions