What task are you trying to do?
Confirm that every package's test:ci script propagates non-zero exit codes through bun turbo test:ci, so a silently-swallowed failure cannot land on green CI.
Context
Split out of #54 (P2 hygiene). Note: fail_on_failure: false at ci.yml:181 is on the JUnit reporter only and does NOT affect unit-job success. The real risk lives in per-package scripts (packages/*/package.json) — if any of them pipe through || true, swallow runner errors, or run background processes without waiting, turbo never sees the failure.
What would a good result look like?
- Each package's
test:ci exits non-zero on at least one intentionally-failing test (spot-check).
- Any script that masks exit codes is fixed or documented.
- A short note in the issue summarizing what was audited.
Audience
Maintainers (CI correctness).
What task are you trying to do?
Confirm that every package's
test:ciscript propagates non-zero exit codes throughbun turbo test:ci, so a silently-swallowed failure cannot land on green CI.Context
Split out of #54 (P2 hygiene). Note:
fail_on_failure: falseatci.yml:181is on the JUnit reporter only and does NOT affect unit-job success. The real risk lives in per-package scripts (packages/*/package.json) — if any of them pipe through|| true, swallow runner errors, or run background processes without waiting, turbo never sees the failure.What would a good result look like?
test:ciexits non-zero on at least one intentionally-failing test (spot-check).Audience
Maintainers (CI correctness).