We looked at the webauthn-device.test.ts e2e failure and don't think our signals SDK update caused it. The test timed out waiting for the Logout button after authenticating with a virtual WebAuthn device, and it has a small but non-zero flake rate. We recommend rerunning the task.
Failed after RBRyan BasView latest
fix(protect): update-signals-sdk
863236ab01Open 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 failing task is @forgerock/journey-suites:e2e-ci--src/webauthn-device.test.ts.
What failed
- 2 tests ran: 1 passed and 1 failed.
- The failure is a 5s
toBeVisibletimeout on the 'Logout' button. - It happened at the authenticate step, after the registration step had already passed.
What the PR changes
- It updates the vendored Ping Protect bundle
packages/protect/src/lib/signals-sdk.js. - It regenerates the api-report markdown files.
- It adds a changeset.
Why this is not a code_change
- The error names no function, import or module touched by the diff.
- The WebAuthn register/authenticate flow in journey-app does not use Protect.
@forgerock/journey-suitesis not intouched_projects.- The failure looks like a UI timing timeout in a browser-driven virtual-authenticator flow, not a deterministic break.
Why this is flaky_task and not environment_state
task_flakiness_ratesreports about 1.4%. That is above 0%, so the task has failed intermittently on the same code before.- No external service is involved. The test runs against localhost servers, so a rerun can go ahead immediately.
Limits of this analysis
- The 1.5 MB diff was not read in full. The judgment relies on the changed-file list and the failing test output.
- No similar-failure branch was provided, so there was no cross-branch comparison.
No code change is proposed. A rerun is the appropriate action.