test(e2e): 공유 fixture build 실패 시험이 잠금을 잡은 쪽을 owner로 둔다 #46

Merged
donghyeon.kang merged 2 commits from donghyeon.kang/test/shared-build-lock-order AGit into main 2026-11-13 08:55:14 +00:00
2 Commits
Author SHA1 Message Date
DongHyeonka f59b4a83ac Merge remote-tracking branch 'origin/main' into test/shared-build-lock-order
frontend-quality-gates / merge / static checks (pull_request) Successful in 1m29s
frontend-quality-gates / merge / tests (pull_request) Successful in 13m54s
frontend-quality-gates / merge / browser tests (pull_request) Successful in 7m12s
frontend-quality-gates / FE-GATE-014 / config-compatibility (pull_request) Skipped
frontend-quality-gates / FE-GATE-028 / manual-accessibility-review (pull_request) Skipped
frontend-quality-gates / FE-GATE-026 / lab-performance (pull_request) Skipped
frontend-quality-gates / FE-GATE-015 / immutable-release-candidate (pull_request) Skipped
frontend-quality-gates / external-vulnerability-provider (pull_request) Skipped
frontend-quality-gates / external-provenance-provider (pull_request) Skipped
frontend-quality-gates / promote-verified-immutable-candidate (pull_request) Skipped
frontend-quality-gates / deploy-promoted-release (pull_request) Skipped
frontend-quality-gates / FE-GATE-019 / hosting-header (pull_request) Skipped
frontend-quality-gates / FE-GATE-021 / runbook-boot-config (pull_request) Skipped
frontend-quality-gates / FE-GATE-022 / runbook-chunk-mismatch (pull_request) Skipped
frontend-quality-gates / FE-GATE-023 / runbook-api-degradation (pull_request) Skipped
frontend-quality-gates / FE-GATE-024 / runbook-telemetry (pull_request) Skipped
frontend-quality-gates / FE-GATE-025 / runbook-release-rollback (pull_request) Skipped
frontend-quality-gates / FE-GATE-018 / field-web-vitals (pull_request) Skipped
frontend-quality-gates / FE-GATE-017 / diagram-review (pull_request) Skipped
frontend-quality-gates / main / self-tests and removal drills (pull_request) Skipped
2026-11-13 16:04:08 +09:00
DongHyeonka 52e1a471a2 test(e2e): 공유 fixture build 실패 시험이 잠금을 잡은 쪽을 owner로 둔다
frontend-quality-gates / merge / static checks (pull_request) Canceled after 0s
frontend-quality-gates / merge / tests (pull_request) Canceled after 0s
frontend-quality-gates / merge / browser tests (pull_request) Canceled after 0s
frontend-quality-gates / FE-GATE-014 / config-compatibility (pull_request) Canceled after 0s
frontend-quality-gates / FE-GATE-028 / manual-accessibility-review (pull_request) Canceled after 0s
frontend-quality-gates / FE-GATE-026 / lab-performance (pull_request) Canceled after 0s
frontend-quality-gates / FE-GATE-015 / immutable-release-candidate (pull_request) Canceled after 0s
frontend-quality-gates / external-vulnerability-provider (pull_request) Canceled after 0s
frontend-quality-gates / external-provenance-provider (pull_request) Canceled after 0s
frontend-quality-gates / promote-verified-immutable-candidate (pull_request) Canceled after 0s
frontend-quality-gates / deploy-promoted-release (pull_request) Canceled after 0s
frontend-quality-gates / FE-GATE-019 / hosting-header (pull_request) Canceled after 0s
frontend-quality-gates / FE-GATE-021 / runbook-boot-config (pull_request) Canceled after 0s
frontend-quality-gates / FE-GATE-022 / runbook-chunk-mismatch (pull_request) Canceled after 0s
frontend-quality-gates / FE-GATE-023 / runbook-api-degradation (pull_request) Canceled after 0s
frontend-quality-gates / FE-GATE-024 / runbook-telemetry (pull_request) Canceled after 0s
frontend-quality-gates / FE-GATE-025 / runbook-release-rollback (pull_request) Canceled after 0s
frontend-quality-gates / FE-GATE-018 / field-web-vitals (pull_request) Canceled after 0s
frontend-quality-gates / FE-GATE-017 / diagram-review (pull_request) Canceled after 0s
frontend-quality-gates / main / self-tests and removal drills (pull_request) Canceled after 0s
문제: `tests/unit/shared-fixture-builds.test.ts`의 「fails the waiting callers
with the builder's failure」가 runner run 235(PR #44, FE-GATE-020 scaffold 사본의
test:coverage)에서 실패했다. 시험은 먼저 부른 호출이 잠금을 잡는다고 가정했다.
그러나 잠금은 key 폴더의 `mkdir`이고, 먼저 끝난 `mkdir`이 주인이 된다. 두 번째
호출(waiter)이 먼저 잡아 빌드했고, 먼저 부른 owner는 기다리는 쪽이 되어 그
성공(`{}`)을 받았다. 구현은 맞고 시험의 가정이 틀렸다(r9-fe 넘김).

고친 것: owner의 builder가 시작될 때(곧 owner가 잠금을 잡았을 때) 알리고,
그 뒤에 waiter를 부른다.

버린 대안: 두 호출에 같은 실패 builder를 주고 결과를 순서 없이 비교하기.
「기다리는 쪽이 빌드한 쪽의 실패를 받는다」를 누가 어느 쪽인지 모른 채
보게 된다.

검증(desktop): 첫 `mkdir`만 30ms 늦추는 일회용 시험에서 옛 시험은 runner와
같은 「promise resolved instead of rejecting」으로 실패하고(RED), 새 시험은
통과했다. 실제 파일 3회 6개 통과, eslint rc=0.
2026-11-13 15:06:20 +09:00