We looked at the failing webauthn-device e2e test and don't think our OpenTelemetry bump caused it. The change only touches e2e/mock-api-v2/package.json, and the failure is a 5s timeout waiting for the 'Logout' button in a browser-driven WebAuthn flow. We recommend rerunning the task.
Failed after Nnx-cloud[bot]View latest
fix(deps): update opentelemetry-js monorepo [Self-Healing CI Rerun]
852659a343Open 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 AI model provider was experiencing issues when this fix was generated.
Why this was not classified as a code change:
The failure is a UI timeout, not a code error.
- One of the two tests in
@forgerock/journey-suites:e2e-ci--src/webauthn-device.test.tspassed. - The other timed out after 5000ms waiting for the 'Logout' button after the authenticate step.
- The output has no import errors, type errors or stack traces pointing at changed code.
- One of the two tests in
The PR diff is unrelated to this test.
- The only changed file is
e2e/mock-api-v2/package.json, where five OpenTelemetry packages are bumped (sdk-logs, sdk-metrics, sdk-trace-base, sdk-trace-node, sdk-trace-web). - The journey-suites e2e code does not reference those packages.
mock-api-v2appears ine2e/journey-suites/package.jsononly as an implicit dependency, and the output shows no sign it was involved.touched_projectscontains '*' only because of the dependency change, not because test code changed.
- The only changed file is
The evidence points to flakiness.
- The task's flakiness rate is about 1.4%, which is above 0%.
- The similar-failure lookup on the other branch returned nothing, so this is not a known base-branch break.
- A timing-sensitive browser flow like this can intermittently miss a short visibility timeout, so a rerun is the right action.
No code changes are proposed.