cesnimda/jobtrackingapp
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

ci: retry frontend build once on silent failure #15

Merged
cesnimda merged 1 commits from ci/retry-frontend-build into main 2026-07-11 19:40:24 +02:00
Conversation 0 Commits 1 Files Changed 1
+6 -1
cesnimda commented 2026-07-11 19:30:55 +02:00
Owner
Copy Link
Copy Source

npm run build has died 3 distinct ways on this runner this session (printed Terser error, explicit SIGSEGV, fully silent kill) -- same resource-starved-runner class already retried for npm ci and dotnet-install elsewhere in this workflow. Retry once, matching that precedent. Unblocks PR #12/#13/#14 which are currently stuck behind this exact flake.

npm run build has died 3 distinct ways on this runner this session (printed Terser error, explicit SIGSEGV, fully silent kill) -- same resource-starved-runner class already retried for npm ci and dotnet-install elsewhere in this workflow. Retry once, matching that precedent. Unblocks PR #12/#13/#14 which are currently stuck behind this exact flake.
cesnimda added 1 commit 2026-07-11 19:30:55 +02:00
ci: retry frontend build once on silent failure
CI and Deploy / test (pull_request) Successful in 1m58s
Details
CI and Deploy / deploy (pull_request) Has been skipped
Details
4f98195592 
npm run build (Terser minify + fork-ts-checker workers) has now died three
distinct ways on this runner in this session: a printed Terser minify error,
an explicit SIGSEGV, and a fully silent kill with zero output between
'Creating an optimized production build...' and the failure line (OOM/SIGSEGV
signature — process killed before it could flush an error). All three are the
same resource-starved-runner class as the npm ci and dotnet-install flakes
already retried elsewhere in this workflow. Retry once, matching that pattern.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
cesnimda merged commit 8edbdceee9 into main 2026-07-11 19:40:24 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
cesnimda
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cesnimda/jobtrackingapp#15
Delete Branch "ci/retry-frontend-build"

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?