We looked at the failing webauthn-device e2e test and found it timed out waiting for the 'Logout' button after the authenticate step. Our PR only bumps @microsoft/api-extractor, a build-time tool, and the diff touches no app or test files. The task also has a non-zero flakiness rate, so we treat this as a flaky failure that should pass on rerun.
Failed after Nnx-cloud[bot]View latest
chore(deps): update dependency @microsoft/api-extractor to v7.59.4 [Self-Healing CI Rerun]
855770a896Open 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.
This was not classified as a code_change for the following reasons.
What failed
- The only failing task is the e2e test src/webauthn-device.test.ts.
- The first test in the file passed.
- The second test failed at line 100, where a 5s toBeVisible check for the 'Logout' button timed out after the authenticate step.
- Task output was present, so the missing-output bail-out did not apply.
Why the PR is not the cause
- The PR is a Renovate bump of @microsoft/api-extractor from 7.58.2 to 7.59.4.
- The PR diff lists no changed files.
- api-extractor only generates API reports and rollups at build time. It cannot plausibly change the runtime behavior of a WebAuthn browser flow.
- The error does not reference any changed function, import or variable.
Flakiness evidence
- The task flakiness rate is about 1.4%, which is above 0%.
- The failure looks like a timing issue, because the UI did not render within 5s during a virtual-authenticator browser flow.
- Earlier self-healing reruns appear in the commit messages, so the failure may persist. That lowers confidence somewhat.
Why no fix is proposed
- No similar-failure branch was provided.
- There is nothing in the PR to fix.
- Skipping or loosening the test is not acceptable, so no code changes are proposed.