We classified this E2E failure as a flaky task rather than a code change because the @forgerock/davinci-suites project was not modified by this release PR, and the test has a historical flakiness rate of ~12%. The 'Registration Complete' heading timeout is consistent with intermittent DaVinci service latency seen in our test environment, and no similar failures were found on main.
Failed after Ggithub-actions[bot]View latest
chore: version-packages
733941bae7Open 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 failing task is @forgerock/davinci-suites:e2e-ci--src/phone-number-field.test.ts, an E2E Playwright test for device registration via PingOne DaVinci flows.
Project not touched by the PR: The PR is a Changesets version-bump release PR (chore: version-packages). The touched_projects list contains only publishable packages (e.g. @forgerock/davinci-client, @forgerock/device-client). The @forgerock/davinci-suites e2e test project was not modified at all.
Error is timing/environment-related: The test failed because the 'Registration Complete' heading never appeared within the 5000ms timeout after clicking Continue in the DaVinci device registration flow. This is a UI timing/service response issue, not a logic error traceable to any diff line.
Historical flakiness confirms non-determinism: The task has a measured flakiness rate of ~12.1%, meaning it fails roughly 1 in 8 runs with the same code. This is consistent with intermittent external service latency or race conditions in the test environment.
No similar failures in main: The similar-task-failure-detector found no matching failures on the main branch, ruling out a pre-existing environment misconfiguration that would warrant an environment_state classification.
Conclusion: All evidence points to a transient, non-deterministic E2E test failure unrelated to the PR's changes. A rerun is expected to pass.