Skip to content

Fix flaky spec on work_packages_table#23877

Merged
oliverguenther merged 1 commit into
release/17.6from
fix/flaky-wp-table-spec
Jun 23, 2026
Merged

Fix flaky spec on work_packages_table#23877
oliverguenther merged 1 commit into
release/17.6from
fix/flaky-wp-table-spec

Conversation

@oliverguenther

Copy link
Copy Markdown
Member

No description provided.

@oliverguenther oliverguenther added the flaky-spec Addresses a Flaky Spec label Jun 23, 2026
@github-actions

Copy link
Copy Markdown

Warning

Flaky specs

  • rspec ./modules/wikis/spec/features/admin/internal_provider_spec.rb[1:1]
🤖 Ask Copilot to investigate

Copy the prompt below into a new comment on this PR to delegate the investigation to GitHub Copilot. It will look into the flakiness and open a separate pull request with you as reviewer.

@copilot The following spec(s) are flaky in CI (first seen on PR #23877, linked for reference only):

- `rspec ./modules/wikis/spec/features/admin/internal_provider_spec.rb[1:1]`

Treat this as a standalone task, unrelated to PR #23877. Create a new branch from origin/dev and open a new pull request targeting dev — do not stack it on PR #23877 or reuse that branch.

Follow the playbook in docs/development/testing/handling-flaky-tests/README.md to find the root cause and fix the underlying race — do not skip, delete, or weaken the spec to make it pass; disabling is a last resort per the playbook, and only with a bug ticket. Verify the fix by running the spec(s) repeatedly (e.g. `script/bulk_run_rspec --run-count 10`).

If you cannot reproduce the flake or are not confident in a fix after reasonable investigation, do not fabricate a change or skip the spec to force CI green. Instead, leave the pull request in draft and document what you tried, the suspected cause, and any leads in its description, then assign @oliverguenther to take over.

Once the fix is verified, title the PR after the spec(s) it fixes, and use the PR description to explain the root cause, how the change resolves it, and the before/after results. Label the PR `flaky-spec`, assign @oliverguenther, and request a review from @oliverguenther.
On every commit, set @oliverguenther as the sole co-author with a `Co-authored-by:` trailer (use their GitHub no-reply email so it links to their account), so it is traceable who dispatched the fix.

@oliverguenther oliverguenther merged commit 31fe489 into release/17.6 Jun 23, 2026
15 checks passed
@oliverguenther oliverguenther deleted the fix/flaky-wp-table-spec branch June 23, 2026 13:45
@github-actions github-actions Bot locked and limited conversation to collaborators Jun 23, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

flaky-spec Addresses a Flaky Spec

Development

Successfully merging this pull request may close these issues.

2 participants