We classified this failure as an environment issue rather than a code regression. All 4 tests time out at the very first UI interaction waiting for DaVinci flow buttons, and the cleanup phase also times out deleting the test user — both pointing to the external PingOne API being unreachable during this CI run. The PR only modifies export structure with no changes to business logic or API communication, so a rerun should resolve this.
Failed after AAAJ AnchetaView latest
chore: add explicit client exports in default entry points
7447178144Open on GitHubSelf-Healing CI
Classification: Environment state
An empty commit was applied to the branch to trigger a new CI pipeline execution to resolve the environment issue.
The PR modifies only export structure: adding a ./fido subpath entry point and making davinci an explicit named export in index.ts. No business logic, API calls, flow processing, or mock server configuration was changed.
The duplicate export concern (export { davinci } in both index.ts and types.ts via export * from './types.js') was investigated but does not cause a failure. Per the ES module specification and TypeScript's resolution rules, an explicit named export always takes precedence over a wildcard re-export — this is valid, produces no build error, and Vite/Rollup handles it correctly.
The Vite WebServer started successfully, meaning the app itself built and loaded without issue.
All 4 tests fail at the exact same point — waitForSelector('button.flow-link', { timeout: 10000 }) — before any test-specific logic executes. This is the very first UI interaction, waiting for DaVinci flow buttons that are rendered in response to an external PingOne API call.
The cleanup phase also fails with a TimeoutError when deleteTestUser attempts to remove the test user via the external PingOne API. Both the flow initialization and the user deletion timing out is a strong indicator that the external PingOne service was unreachable during this CI run, not that any code path was broken.
The flakiness rate is 0%, which reflects historical consistency when the external service is available — it does not account for transient external service outages. No similar failures were found in other branches, consistent with other branches having run at a time when the external service was available.