We looked into the failing journey-suites WebAuthn e2e test and found it is unrelated to our changes, which only add Mend scan GitHub workflow and action files. The same failure (Logout button not visible after authenticating) also appears on branch 852, so it is pre-existing and we are not proposing a fix in this PR.
Failed after AAAJ AnchetaView latest
ci: add Mend scan workflow for releases
8624f7db53Open on GitHubSelf-Healing CI
Classification: Environment state
No code changes are applicable.
The AI model provider was experiencing issues when this fix was generated.
This failure was not classified as a code change, for these reasons:
The PR only adds Mend SAST GitHub Actions files:
.github/actions/mend-sast/action.yml,.github/actions/mend-setup/action.yml, and.github/workflows/mend-release-scan.yml. The only touched project isforgerock-verdaccio. No application, test, or e2e code was modified.The failing task is
@forgerock/journey-suites:e2e-ci--src/webauthn-device.test.ts. It fails at line 100, wheregetByRole('button', { name: 'Logout' })is not visible after the WebAuthn authenticate step. Nothing in the diff touches that test, the journey app, or the mock API.The same failure appears on branch 852. It is the same test, the same line 100, and the same locator and timeout. Under the decision process, a matching failure on another branch means the PR did not cause it, so it is classified as environment_state. It should be fixed in its own PR, not here.
The flakiness rate is low, about 1.4%. That does not change the outcome, because the failure is already shown to exist independently of this PR.
No code changes are proposed.