ping-javascript-sdk
Failed after Nnx-cloud[bot]
View latest

fix(protect): update-signals-sdk [Self-Healing CI Rerun]

8635f753a2Open on GitHub

Self-Healing CI

Classification: Flaky task

We looked at the failing webauthn-device e2e test, and it looks unrelated to our changes. Our PR only updates the protect signals SDK and generated api-report files, and the test timed out after 5s waiting for the Logout button in a flow we didn't touch. The task has a small non-zero flakiness rate (~1.4%), so we think a rerun is the right next step.

An empty commit was automatically applied to the branch to trigger a new CI pipeline execution to resolve the flaky task.

The failure was classified as flaky_task, not code_change, for these reasons:

  1. The failure is a timeout, not a code error.
  • In src/webauthn-device.test.ts, the "Authenticate with the registered WebAuthn device" step timed out after 5000ms waiting for the Logout button.
  • The registration step and the other test in the file passed.
  • The error is a short UI-visibility timeout in a browser flow that uses a virtual authenticator and a mock server. That points to timing.
  1. The PR does not touch the code path the test exercises.
  • The diff changes only the bundled protect signals SDK (packages/protect/src/lib/signals-sdk.js), a changeset, and generated api-report markdown files.
  • None of these are in the WebAuthn register/authenticate flow.
  • The journey-suites project is not in touched_projects.
  1. The task has a non-zero flakiness rate.
  • The rate is about 1.4%, which means it does sometimes fail on the same code.
  1. No code fix is justified.
  • No specific changed lines can be tied to the error.
  • Removing the PR's changes would not logically fix a 5s UI timeout in an unrelated flow.
  • The right action is to rerun the task, so no changes were made.
  1. One check was not run.
  • No similar-failure branch was provided in the input, so the similar-task-failure-detector subagent was not used.