You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit a349d71
Browse filesBrowse the repository at this point in the historyBrowse files
chore: fail-fast CI hangs + refresh README header (#75)
* chore: fail-fast CI hangs + refresh README header
Recent main runs (notably the v0.0.28 bump) burned the full 60-min job
budget on `10_env_command.sh` hanging in xlings install on a fresh
MCPP_HOME. The hang is intermittent and lives at the network boundary;
no fix to xlings itself in this PR — just shorten the feedback loop.
CI:
- tests/e2e/run_all.sh wraps every test with `timeout 600` (override via
E2E_TEST_TIMEOUT). Distinguishes TIMEOUT (exit 124) from regular FAIL
and surfaces the offending test name in the summary. Uses `timeout` if
available, falls back to `gtimeout` (macOS coreutils), else skips
wrapping and relies on the step-level guard.
- ci.yml / ci-macos.yml / ci-windows.yml: add `timeout-minutes: 25` to
each "E2E suite" step. A hung suite now fails in ~25 min instead of
eating the full 60-min job, freeing the toolchain test steps to still
run / be diagnosed.
README:
- Add a prominent links table directly under the badges: docs / quick
start / mcpp.toml guide / examples / toolchains on row 1; package
index, mcpplibs, forum, Issues, Releases on row 2.
- Add live CI status badges for Linux/macOS/Windows; drop the static
"Self-hosted" badge that the CI badges now subsume.
- Promote Windows x86_64 LLVM/Clang from 🔄 to ✅ (CI is green since
v0.0.27); add footnote noting the MSVC BuildTools dependency and the
llvm-mingw direction.
* chore: rename ci.yml → ci-linux.yml; move CI status into README table
- Workflow renamed (and `name:` updated) to match the platform-prefixed
ci-macos / ci-windows convention. Comment cross-references updated.
- README: drop the 3 CI badges from the badges row and add them as the
table's last row alongside the docs / community links — keeps the
badges row focused on project metadata (release / language / license).
0 commit comments