We looked at the failing WebAuthn e2e test and found nothing in our SWC dependency bump that could cause it. The test timed out after 5s waiting for the 'Logout' button, which looks like a timing issue, and the task has a small non-zero flake rate. We recommend rerunning it rather than changing code.
Self-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 SWC dev dependencies (@swc/core, @swc-node/register, @swc/helpers). It changes no application code, functions or imports.
The failing task is the Playwright test
@forgerock/journey-suites:e2e-ci--src/webauthn-device.test.ts.- Registration succeeded, and the other test in the file passed.
- The failure came at the authenticate step.
getByRole('button', { name: 'Logout' })was not visible within the 5000ms timeout.
The error does not name any changed code.
- It shows only a UI wait timeout.
- No line in the diff can be identified as the cause.
- Removing the dependency bump would not obviously fix the failure.
The flow relies on a virtual WebAuthn authenticator, a browser and the mock AM server. It has timing-sensitive waits.
The task's flakiness rate is above 0% (about 0.7%), so it has failed before on identical code.
touched_projects contains '*', but that comes from the lockfile change. It is not evidence that this test is affected.
The failure is classified as flaky_task. No files were changed, and a rerun is recommended.
The similar-task-failure-detector subagent was not run, so a matching failure on another branch was not ruled out.