Skip to content

ci: control run — baseline shard a (do not merge) - #2118

Closed
renemadsen wants to merge 1 commit into
stablefrom
ci/control-shard-a-baseline
Closed

ci: control run — baseline shard a (do not merge)#2118
renemadsen wants to merge 1 commit into
stablefrom
ci/control-shard-a-baseline

Conversation

@renemadsen

Copy link
Copy Markdown
Member

Control experiment, not for merge.

PR #2117 fails items-planning-playwright-test (a) on items-planning-settings.spec.tsshould go to plugin settings page, with Target page, context or browser has been closed. It reproduced on a re-run.

That test logs in, opens the plugins page and reads a table row. It does not load any component #2117 touches (pairing-grid-update, planning-assign-sites-modal, planning-multiple-delete, plannings-bulk-import-modal), and #2117's workflow step sits in the build job, which passes.

This repo last ran CI two months ago, so there is no recent baseline. This branch is untouched stable plus one whitespace character, built against the current frontend stable. If shard a fails here too, the failure is pre-existing and unrelated to #2117.

Close once it has reported.

Only a trailing comment. The previous attempt touched README.md, which the
workflow ignores via paths-ignore, so no CI ran at all.

Purpose: determine whether items-planning-settings.spec.ts 'should go to
plugin settings page' fails on untouched stable against the CURRENT
eform-angular-frontend stable. This repo last ran CI two months ago, so PR
#2117 had no baseline for its shard-a failure.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015sXLtgzZU8QL9m84GqMkoJ
@renemadsen
renemadsen force-pushed the ci/control-shard-a-baseline branch from 8691c1f to 285fcb2 Compare August 24, 2026 10:30
@renemadsen

Copy link
Copy Markdown
Member Author

Control complete. Shard a fails identically on untouched stable — same test (items-planning-settings.spec.tsshould go to plugin settings page), same error (Target page, context or browser has been closed).

That confirms the failure is pre-existing and unrelated to #2117, which is now merged.

Worth a separate look: this repo last ran CI two months ago, and the failure reproduces on a clean checkout against the current frontend stable, so something in that gap broke plugin-activation e2e. The error is a browser/page closure rather than an assertion, and the server logs show no application error.

@renemadsen renemadsen closed this Aug 24, 2026
@renemadsen
renemadsen deleted the ci/control-shard-a-baseline branch August 24, 2026 10:42
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