We looked at the failing webauthn-device e2e test and don't think our eslint-plugin-playwright bump caused it. The test timed out after 5s waiting for the Logout button, and the task has a non-zero flakiness rate. We suggest rerunning it, with no code change.
Failed after Rrenovate[bot]View latest
chore(devdeps): update dependency eslint-plugin-playwright to v2.12.1
860318760aOpen on GitHubSelf-Healing CI
Classification: Flaky task
An empty commit was automatically applied to the branch to trigger a new CI pipeline execution to resolve the flaky task.
The AI model provider was experiencing issues when this fix was generated.
Why this was not classified as a code_change:
The PR only bumps the eslint-plugin-playwright devDependency from 2.10.2 to 2.12.1.
- It is a lint-only plugin and does not affect runtime behavior of the e2e tests or the apps under test.
- The PR diff listed no changed source files.
The failure is a timing-dependent UI assertion, not a reference to changed code.
- The failing task was @forgerock/journey-suites:e2e-ci for src/webauthn-device.test.ts.
- One of the two tests passed. The other failed at the "Authenticate with the registered WebAuthn device" step.
- That step ran expect(getByRole('button', { name: 'Logout' })).toBeVisible() and timed out after 5000ms.
- The error mentions no lint rule, import, function or variable touched by the PR.
The task has a flakiness rate of 1.25%, which is above 0%.
- The project is only marked as touched because the dependency change counts as a global change (touched_projects contains '*').
- The error itself is not connected to the change, so the flakiness evidence outweighs that default.
Task output was present for the failing task, so the missing-output bail-out did not apply.
- No similar-failure branch was provided, so the similar-task-failure-detector was not used.
Conclusion: the failure is non-deterministic and timing-related, so a rerun is appropriate. No code changes are proposed.