We looked at the WebAuthn e2e failure and it does not look related to our api-extractor bump. The 'Logout' button did not show up within 5s after the authenticate step, which points to a timing issue. This test has a small but non-zero flake rate, so we expect a rerun to pass.
Failed after Nnx-cloud[bot]View latest
chore(deps): update dependency @microsoft/api-extractor to v7.59.4 [Self-Healing CI Rerun]
855ba7603eOpen 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 PR only bumps @microsoft/api-extractor from 7.58.2 to 7.59.4.
- It is a build-time tool for API reports and d.ts rollups.
- The PR diff lists no changed source files.
The failing task is a Playwright e2e test (webauthn-device.test.ts).
- In the 'Authenticate with the registered WebAuthn device' step,
expect(getByRole('button', { name: 'Logout' })).toBeVisible()timed out after 5000ms. - The other test in the same run passed, and the registration steps before this point worked.
- In the 'Authenticate with the registered WebAuthn device' step,
The error does not reference any code, import or behavior affected by the dependency change.
The task has a flakiness rate of about 1.4%, which is above 0.
- The failure is a timing-sensitive wait on a localhost WebAuthn browser flow.
- That fits a non-deterministic failure that a rerun should clear.
No code changes are proposed.