fix(ci): kill the Windows child via taskkill, not a signal

Review found kill -TERM against a native Windows binary (bun.exe)
under Git Bash is best-effort thread injection, not a real
signal, and can fail to land -- reproducing the exact hang this
watchdog exists to prevent. taskkill //F //T is a real
TerminateProcess call.

Also: cite the run id instead of a branch name (branches get
deleted), and add the missing shell: bash the repo's other
Windows steps already set explicitly.
This commit is contained in:
Miguel Angel Simon Sierra
2026-09-19 19:17:17 -04:00
parent 33145fa4b6
commit 7ff370de5c
3 changed files with 11 additions and 2 deletions
+1 -1
View File
@@ -105,7 +105,7 @@ COPY packages/engine/package.json packages/engine/
COPY packages/producer/package.json packages/producer/
# A corrupt tarball extraction can print an error and then hang instead of
# exiting (fix/regression-docker-build-timeout). Bound each attempt and retry.
# exiting (run 35468046055). Bound each attempt and retry.
RUN npm install --global bun && \
(timeout 300 bun install --frozen-lockfile || timeout 300 bun install --frozen-lockfile) && \
npm uninstall --global bun