Skip to content

test(webkit): DO NOT MERGE - webkit GC leak matrix on macos-15-xlarge - #42680

Draft
Yury Semikhatsky (yury-s) wants to merge 3 commits into
microsoft:mainfrom
yury-s:webkit-gc-repro-do-not-merge
Draft

test(webkit): DO NOT MERGE - webkit GC leak matrix on macos-15-xlarge#42680
Yury Semikhatsky (yury-s) wants to merge 3 commits into
microsoft:mainfrom
yury-s:webkit-gc-repro-do-not-merge

Conversation

@yury-s

Copy link
Copy Markdown
Member

Summary

Diagnostic only — do not merge. Pushed to get one signal off macos-15-xlarge.

  • page-leaks.spec.tsexpect should not leak has failed ~70% of runs on webkit-macos-15-xlarge since 2dec18d7e (roll to WebKit r2359), while the click/fill/waitFor tests beside it are 0/88. This adds a variant matrix over the same scenario — one test per locator call, plus raw-DOM equivalents — to find out whether that asymmetry is real or a timing artifact.
  • A standalone reduction hit wholesale retention on the waitFor equivalent, which does not fit the expect-specific story.
  • Every other workflow is removed on this branch so nothing but the WebKit leak job runs.

Diagnostic branch. Runs page-leaks plus a per-operation variant matrix on the
one bot that reproduces the r2359 GC regression, to determine whether the
failure really is confined to the expect path.

All other workflows are removed on this branch so the draft PR runs nothing else.
First run showed waitFor failing 10/10 here while page-leaks' own waitFor test
passed 10/10 on the same bot. The tests differ only in that the expect test
registers WeakRefs before the loop as well as after, and every variant here
copies that shape.

These two controls drop the pre-loop registration to confirm it is a necessary
ingredient rather than the assertion path.
Resolves the modify/delete conflict that blocked CI: a conflicting PR has no
merge ref, so GitHub skipped the pull_request workflow entirely and the second
commit never ran.

Only the 8 workflows that can fire on a pull_request stay deleted. The other 13
are restored - they trigger on issues, schedule, workflow_dispatch,
workflow_call, workflow_run, or push to release-*, none of which a PR can
reach - which shrinks the conflict surface from 21 files to 8.
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