We reviewed all 16 failing e2e tasks and determined they are pre-existing infrastructure failures unrelated to this PR's changes. The errors — recursive Nx task loops, localhost port conflicts (5829, 8443), and downstream connection-refused failures — appear identically on the main branch, confirming they were not introduced here. No code fix is needed; a CI rerun should resolve the transient port contention.
Failed after VPVatsal ParikhView latest
feat: add AM mediation check to WebAuthn and export storage config types
762315063fOpen 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 AI model provider was experiencing issues when this fix was generated.
All 16 failing tasks are e2e test suites in @forgerock/davinci-suites, @forgerock/journey-suites, and @forgerock/oidc-suites — none of which appear in the PR's touched_projects list (["forgerock-verdaccio","@forgerock/journey-app","@forgerock/journey-client","@forgerock/oidc-client"]).
The PR's changes are confined to:
- @forgerock/journey-client: adding an optional
stepparameter toWebAuthn.isConditionalMediationSupported - @forgerock/oidc-client: re-exporting
BrowserStorageConfig,CustomStorageConfig, andCustomStorageObjectfrom the types entry point
No e2e test configuration, Playwright config, Nx task graph, or port assignments were modified.
The failures fall into three infrastructure error categories:
Recursive Nx task invocation (@forgerock/davinci-suites:e2e-ci--src/qr-code.test.ts): Nx detected the loop: davinci-app:serve → davinci-app:nxServe → e2e-ci → davinci-app:serve. This is a pre-existing Nx task configuration issue — nothing in the diff touches task or project configuration.
Port already in use (multiple journey-suites and oidc-suites tasks): Errors of the form "http://localhost:5829 is already used" and "http://localhost:8443 is already used" indicate concurrent CI test processes competing for the same ports — a pre-existing infrastructure/scheduling problem.
Connection refused / element not found (davinci-suites protect, form-image, form-fields, password-policy): These are downstream consequences of the server never starting successfully due to the above infrastructure issues.
Verification via the similar-task-failure-detector agent confirmed that the recursive loop, localhost:5829 port conflicts, and davinci protect connection-refused errors appear identically on the main branch, proving they predate this PR.
The additional failures present in this branch but not on main (10 extra tasks) show the exact same port-conflict and connection-refused patterns, consistent with run-to-run variability in how aggressively CI schedules concurrent test workers — not with any code change.