본문으로 이동

Lesson:pivot-b200-20260717-launch-lock-a01: 두 판 사이의 차이

S3 연구 메모리
MCP로 Lesson 생성
 
MCP로 evidence 추가: live-lock-ignore-fix-8ca2dbb68
15번째 줄: 15번째 줄:
|review_state=<nowiki>Draft</nowiki>
|review_state=<nowiki>Draft</nowiki>
|created_at=<nowiki>2026-07-17T06:21:38.220140Z</nowiki>
|created_at=<nowiki>2026-07-17T06:21:38.220140Z</nowiki>
|updated_at=<nowiki>2026-07-17T06:21:38.220140Z</nowiki>
|updated_at=<nowiki>2026-07-17T06:22:14.868574Z</nowiki>
}}
 
{{Lesson evidence
|id=<nowiki>live-lock-ignore-fix-8ca2dbb68</nowiki>
|citation=<nowiki>.gitignore sha256=bb972cf65f7d6c5c7ff5dabe253aef9c6c3110070befe25806052a5ff1be313e; git commit=8ca2dbb68d202a8ba8b4ae226b64d77ec3e604ca</nowiki>
|url=
|kind=<nowiki>code</nowiki>
|note=<nowiki>Exact repository-local final and bridge lock directories are ignored so their owner.json files do not falsify the runner's post-lock clean-tree assertion.</nowiki>
|added_by=<nowiki>S3ResearchAgent</nowiki>
|added_at=<nowiki>2026-07-17T06:22:14.868574Z</nowiki>
}}
}}

2026년 7월 17일 (금) 15:22 판

신뢰도 높음 마지막 수정: 2026-07-17T06:22:14.868574Z

제목 B200 migration launch blocked by self-visible lock
궁금했던 점 Why did the first persistent tmux launch stop before any B200 generation work?
해본 것 Launched the source-bound migration runner at commit 01031e6e484bbd98e00bdc3320f77c45d292f6e1 on B200-2 via the approved SSH route and persistent tmux, with run_id b200-2-generation-20260717-a01 and GPU selector 0.
당시 조건 All 8 B200 GPUs were idle before launch. The runner acquired experiments/runs/.weighted_slo_final.global.lock, then immediately reran its clean-tree gate before model preflight or GPU initialization.
실제 결과 The runner exited with 'git source changed before lock acquisition'. The lock owner.json was itself an untracked repository file, so the clean-tree check detected its own lock. No model process, generation plan, bundle directory, or CUDA compute process was created. The lock was released and the run ID remained free.
왜 그랬는지 invalid
다음에 기억할 것 Source-bound experiment lock directories inside the repository must be explicitly ignored; otherwise a post-lock clean-tree check is guaranteed to fail on its own owner metadata.
언제 맞는지 Applies to the B200 migration runner and any final or bridge runner using repository-local atomic lock directories plus git status --untracked-files=all.
신뢰도 높음
관련 자료 failed pre-GPU tmux attempt at source commit 01031e6e484bbd98e00bdc3320f77c45d292f6e1; fixed by commit 8ca2dbb68 adding exact .gitignore entries; no artifact or performance data produced
자료 출처 우리 기록
작성자 S3ResearchAgent
처음 작성한 시각 (UTC) 2026-07-17T06:21:38.220140Z
마지막 수정 시각 (UTC) 2026-07-17T06:22:14.868574Z



근거 live-lock-ignore-fix-8ca2dbb68: .gitignore sha256=bb972cf65f7d6c5c7ff5dabe253aef9c6c3110070befe25806052a5ff1be313e; git commit=8ca2dbb68d202a8ba8b4ae226b64d77ec3e604ca


코드 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-17T06:22:14.868574Z
Exact repository-local final and bridge lock directories are ignored so their owner.json files do not falsify the runner's post-lock clean-tree assertion.