test: timing budgets + CI hardening (artifact v3 pin, npm cache retry) #69
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "test/timing-budgets-ci-hardening"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes three items from the outstanding e2e/CI gap list:
Timing budgets:
timings.measure()only ever recorded durations forthe (still-unwired) Pushgateway export — nothing failed CI when a step
got slow. Adds
e2e/timing-budgets.ts(expectWithinBudget+ sharedBUDGET_MSbuckets) and wires it into everymeasure()call site acrossthe suite. Mail-wait steps are deliberately left unbudgeted (external
mail-trap delivery latency, not a code performance signal).
actions/upload-artifact@v4doesn't work against this Gitea/actrunner's artifact backend — pinned to v3 for the e2e failure-report
upload.
npm cache corruption retry: the shared act_runner npm cache has
corrupted platform-native tarballs before (
@next/swc-linux-x64-musl)and reds
viewer-unit/admin-unit/e2ewith no product bug involved.All three
npm cisteps now retry once afternpm cache clean --forceon first failure.
ROADMAP.md / e2e/README.md updated to reflect all three as closed.
Test plan
npx tsc --noEmitclean ine2e/no budget-assertion failures)