fix: flaky 성능 테스트 강건화 (PR #35 CI 실패 원인)#36
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR #35 CI에서 터진 test_doc_store_performance의 10배 비율 단언은 공유 러너 타이밍 노이즈에 취약한 단발 측정이었음(SQL 11ms vs JSON 1ms). 3회 측정 최솟값으로 강건화 — 절대 상한(<0.5s)과 비율 계약은 유지. 사후 기록: #35는 CI 실패 상태로 머지됨(팀리드 절차 실수 — watch와 merge를 한 체인에 넣어 exit 미확인). 실패 원인이 본 PR 무관 flake임을 확인했고 재발 방지로 merge는 CI exit 확인 후 별도 실행으로 전환.