We looked at the webauthn-device e2e failure and don't think our changes caused it. The test timed out after 5s waiting for the Logout button, and we only updated the protect signals SDK and regenerated API reports, none of which this test exercises. The task also has a nonzero flakiness rate, so we recommend rerunning it.
Failed after Nnx-cloud[bot]View latest
fix(protect): update-signals-sdk [Self-Healing CI Rerun]
8631939977Open 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.
Why this was not classified as a code change:
- The failure itself
- The Playwright test src/webauthn-device.test.ts timed out at line 100. It expected the Logout button to be visible within 5000ms after the authenticate step.
- The register step passed, and the other test in the file passed.
- The PR does not touch this code path
- The PR changes only packages/protect/src/lib/signals-sdk.js, regenerated api-report markdown files, and a changeset.
- None of these are on the WebAuthn journey path that the test exercises.
- @forgerock/journey-suites is not in touched_projects.
- Flakiness evidence
- The task flakiness rate is about 1.4%. That is above 0, so the task has failed intermittently on the same code before.
- A short visibility timeout after a virtual-authenticator round-trip points to a timing issue.
- Limits of the analysis
- The similar-task-failure-detector subagent was not run, so a matching failure on the base branch was not ruled out.
Conclusion: no error message or diff line links the failure to the changes. It is classified as flaky_task, and a rerun is recommended. No code changes are proposed.