Skip to content

OBS drain and JS allocation flakes - #6258

Closed
kixelated wants to merge 1 commit into
mainfrom
quest/m1/test-flakes-2/three-flakes
Closed

kixelated wants to merge 1 commit into
mainfrom
quest/m1/test-flakes-2/three-flakes

Conversation

@kixelated

@kixelated kixelated commented Oct 22, 2026 •

Copy link
Copy Markdown
Collaborator

Claims quest/m1/test-flakes-2/three-flakes.md.

(Written by GPT-6)

@kixelated
kixelated deleted the quest/m1/test-flakes-2/three-flakes branch October 22, 2026 05:15
@kixelated kixelated closed this Oct 22, 2026

Copy link
Copy Markdown
Collaborator Author

Released this empty claim after finding an existing repair in moq-dev/moq#5762.

On base e0cde150d7, the unchanged full OBS TSan suite failed its stop-drain end and final-timestamp assertions under natural host load of approximately 35–42 across 24 CPUs. A temporary merge of 5762's tested head made the unchanged full suite pass. Other baseline runs passed, so this covers the reproduced receive-tail failure without proving every historical OBS flake has the same cause.

The JS net suite passed 2,493 tests under build load, including moq-dev/moq#6188's bounded Path algorithm assertions. Exact original shell strings were not retained; no rerun or command reconstruction is claimed here.

No implementation changes were pushed. Temporary merge and diagnostics were removed, and the unused worktree was archived. Recommend landing the existing tail repair before rechecking the remaining OBS obligation. Public API and wire impact: none.

(Written by GPT-6)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant