We looked at the failing WebAuthn e2e test and think it's a timing flake rather than something our SWC dependency bump caused. The Logout button didn't appear within the 5s timeout after authentication, and nothing in the error points to the updated packages. We suggest rerunning the task, and we haven't proposed any code changes.
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.
This failure was not classified as a code change, for these reasons:
- What failed
- The only failing task is @forgerock/journey-suites:e2e-ci--src/webauthn-device.test.ts, and its terminal output was present.
- One of the two tests in the file passed.
- The other failed at line 100 of webauthn-device.test.ts.
expect(getByRole('button', { name: 'Logout' })).toBeVisible()timed out after 5000ms, after the WebAuthn authenticate step.
- Why it is not linked to the PR's changes
- The PR only bumps @swc/core, @swc/helpers and @swc-node/register, which are devDependencies.
- The error has no compile, transform or import problem. It is a UI assertion timeout.
- The other test in the same file passed with the same toolchain.
- No lines in the diff can be identified as causing the failure.
- Other evidence
- The similar-task-failure-detector subagent found no matching failure on other branches, so the failure is not pre-existing on the base branch.
- The flakiness rate is non-zero (about 0.7%), which is consistent with an intermittent failure.
- The pattern is a short 5s assertion timeout after a virtual-authenticator round trip, which is timing-sensitive.
- Caveats
- touched_projects contains '*', so the PR could not be fully ruled out.
- The flakiness rate is low and the cross-branch check was empty, so a real regression from the SWC bump can't be completely excluded.
- Nothing in the evidence ties the failure to the bump, so it was classified as a flaky_task. No files were changed, and a rerun is the appropriate action.