fix(ci): 실패한 ci:gate가 실패한 명령, 로그 경로, 로그 끝줄을 말한다 #30
Closed
donghyeon.kang
wants to merge 0 commits from
donghyeon.kang/fix/r9-gate-failure-output AGit into main
pull from: donghyeon.kang/fix/r9-gate-failure-output
merge into: :main
:main
:fix/r9-structure-locale
:fix/r9-adapter-carryover
:test/shared-build-lock-order
:ci/dependency-cache-same-filesystem
:ci/release-tag-for-a11y-review
:ci/merge-dependency-cache
:fix/test-timeouts-measured
:fix/feature-residue-word-boundary
:fix/provider-wait-stderr
:fix/provider-job-host-requirements
:fix/ungated-vitest-spec
:fix/a11y-evidence-routes
:fix/verify-parts-diagnostics
:claude/w2-fe-ci-perf-dce080
:fix/child-process-test-timeouts
:chore/layout-rules-r2-r5
:claude/fe-b-docs-korean-645f55
:chore/ci-merge-jobs
:chore/layout-3-merge
:claude/fe-c-harness-0ae061
:chore/layout-2-sample-removal
:chore/layout-1-cleanup
:docs/review-guide-pointer
:fix/maturity-review-2026-11-06
:fix/maturity-review-2026-11-05-b
:docs/improvement-manual
:fix/maturity-review-2026-11-05
:fix/session-subject-required
:fix/ui-design-audit-2026-11-01
:fix/maturity-review-2026-09-25
:lane/D
:lane/B
:fix/src-review-round3
:refactor/domain-scalable
:develop
:feature-frontend-optional-adapter-recipes
:feature-frontend-supply-chain-verification
:feature-frontend-test-registry-evidence-hardening
:frontend-test-registry-evidence-hardening
:feature-frontend-diagnostics-telemetry-runtime
:feature-frontend-i18n-message-formatting-contract
:feature-frontend-design-system-platform
:feature-frontend-form-page-platform
:feature-frontend-reference-feature-vertical-slice
:feature-frontend-routing-release-recovery-runtime
:feature-frontend-http-query-contract-execution
:feature-frontend-application-boundary-runtime
:feature-frontend-typescript-tooling-foundation
:feature-frontend-platform-capability-review
:feature-frontend-performance-route-contract
:feature-frontend-starter-experience-quality-contract
:feature-frontend-responsive-theme-contract
:feature-frontend-ui-primitives-gallery-contract
:feature-frontend-app-shell-navigation-contract
:feature-frontend-runtime-composition-contract
:feature-frontend-ci-quality-gates-contract
:feature-web-vitals-performance-budget-contract
:feature-frontend-release-cache-rollback-contract
:feature-accessibility-baseline-contract
:feature-frontend-project-bootstrap-toolchain-contract
:feature-frontend-operational-runbook-contract
:feature-frontend-contract-compatibility-governance
:feature-frontend-contract-registry-governance
:feature-frontend-browser-security-boundary-contract
:feature-frontend-build-bundle-supply-chain-contract
:feature-tailwind-design-token-styling-contract
:feature-sample-feature-slice-contract-fixture
:feature-frontend-render-recovery-boundary-contract
:feature-routing-navigation-guard-contract
:feature-boundary-mapper-viewmodel-contract
:feature-async-ui-state-contract
:feature-frontend-observability-logging-trace-contract
:feature-frontend-storage-registry-contract
:feature-server-state-caching-contract
:feature-frontend-auth-session-integration-contract
:feature-frontend-error-classification-boundary-contract
:feature-runtime-schema-validation-contract
:feature-api-client-response-envelope-contract
:feature-frontend-env-runtime-config-contract
:feature-frontend-architecture-enforcement-lint-contract
:feature-frontend-test-taxonomy-contract
:feature-frontend-clean-architecture-layering-contract
No Reviewers
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
donghyeon.kang (동현 강)
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: donghyeon.kang/clean-architecture-frontend-template#30
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
무엇을, 왜
corepack pnpm ci:gate <ID>가 실패하면 콘솔에는FE-GATE-013 security: FAIL한 줄만 나온다. 어느 명령이 실패했는지, 원인이 남은 로그가 어디인지 말하지 않는다.verify.sh의 게이트 로그도 그 세 줄뿐이라 원인을 보려면artifacts/quality/gates/아래 로그를 따로 찾아야 한다. 규칙(.claude/rules/gates-and-budgets.md)은 실패 메시지가 넘은 항목·잰 값·고칠 파일을 말하라고 한다(1112/08-13). 이 round에서도 F8 문서 게이트 실패의 원인을 찾느라 같은 일을 했다.고른 방법과 버린 대안
scripts/lib/ci-gate-failure.ts의formatGateFailure가 FAIL 줄, 실패한 명령(없으면 명령 밖 검사라고), 로그 경로, 로그 끝 20줄을 만든다.scripts/run-ci-gate.ts가 기대에 어긋난 명령을 기억해 넘긴다.tests/system/ci-runner와 같은 임시 root 방식으로 FE-GATE-004의 명령 하나를 일부러 실패시킨 계약을run-ci-gate.ts로 돌려 stderr를 보는 시험을 더했다(커밋36f8c00f). timeout은 같은 방식 시험의 잰 값을 쓴다.위험과 영향
검증
desktop, CI env,
scripts/verify.sh(flock).5250ff95에 새 시험만):tests/unit/ci-gate-failure.test.ts모듈이 없어 실패. 로그/tmp/claude-gates/r9f9-red/./tmp/claude-gates/r9f9-green/.36f8c00f):ci-gate-failure.test.ts4 passed.run-ci-gate.ts에서failedCommand = commandLine;을 지운 변이에서는 새 시험이 실패한다(stderr가failed command: none …). 로그/tmp/claude-gates/r9f9b/.f87ac5b3= head 트리): FE-GATE-002 rc=0, FE-GATE-003 rc=0. FE-GATE-013은 rc=1이다. desktop 호스트가 unprivileged user namespace를 막아test:system의 사전 점검이 실패한다(결정 D8의 그 실패). 그 실패에서 새 출력이 나왔다:failed command: $ corepack pnpm test:system,log: artifacts/quality/gates/FE-GATE-013.txt, 사전 점검이 낸 원인 줄. 로그/tmp/claude-gates/r9f9-gates/.리뷰어가 볼 곳
scripts/run-ci-gate.ts의failedCommand.관련
docs/reviews/2026-11-round9-08-guardrails-docs.md08-13(PR #23)#40으로 병합됐다(main
ee47480c). 이 PR의 headfb1ca6af가 #40 브랜치에 merge 커밋으로 들어 있고, #40의 runner merge job 셋이 그 합친 트리로 초록이었다. runner 대기를 줄이려고 이번만 쓴 방식이다(소유자 승인, 2026-11-13).Pull request closed