We looked at the failing webauthn-device e2e test, and it timed out waiting for the Logout button after WebAuthn authentication. Our changes only touch the protect signals SDK and the generated API reports, which this flow doesn't use. The task has a nonzero flakiness rate (1.4%), so we expect it to pass on rerun.
Failed after Nnx-cloud[bot]View latest
fix(protect): update-signals-sdk [Self-Healing CI Rerun]
863ae8fa44Open 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.
This failure was not classified as a code_change for the following reasons.
- The failure itself:
- The failing task is @forgerock/journey-suites e2e webauthn-device.test.ts.
- The step 'Authenticate with the registered WebAuthn device' timed out after 5s waiting for the Logout button.
- The other test in the file passed, and registration succeeded earlier in the same test.
- No link to the PR changes:
- The PR changes only packages/protect/src/lib/signals-sdk.js, regenerated api-report markdown files and a changeset.
- The WebAuthn device flow does not use the Protect signals SDK.
- The journey-suites project is not in touched_projects.
- The error does not reference any changed function, import or variable.
- Signs of flakiness:
- The task's flakiness rate is about 1.4%, so it has failed intermittently on identical code before.
- The failure is a short assertion timeout on a browser WebAuthn authentication step, which is timing-dependent.
- Not checked:
- The similar-failure detector was not run against other branches.
No code change is proposed. Rerunning the task is the appropriate action.