We looked at the failing WebAuthn e2e test (Logout button not visible after authenticate), and it is unrelated to our changes, which only add Mend scan workflow and action files. The same failure also appears on branch 852, so it predates this PR and we are not proposing any fix here.
Failed after AAAJ AnchetaView latest
ci: add Mend scan workflow for releases
862c66ce45Open 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.
The failing task is @forgerock/journey-suites:e2e-ci--src/webauthn-device.test.ts.
It fails at webauthn-device.test.ts:100. The 'Logout' button is not visible within 5000ms after the authenticate step.
Why this is not a code_change:
- The PR only adds .github/actions/mend-sast/action.yml, .github/actions/mend-setup/action.yml and .github/workflows/mend-release-scan.yml.
- None of these files touch journey-suites, journey-app or any runtime code the test exercises.
- The error does not reference anything changed in the diff.
- The similar-task-failure-detector found the identical failure on branch 852. It has the same test, line, locator, timeout and "element(s) not found" error.
- Because the failure exists on another branch, this PR did not cause it. Per the decision process, that makes it environment_state, and a fix should not be proposed in this PR.
Why it is not flaky_task:
- The flakiness rate is about 1.4%, and the failure is reproduced identically on another branch, so it looks like a consistent pre-existing issue rather than an intermittent one.
No files were changed. Analysis was done by reading the task output, the PR file list, the flakiness rate and the cross-branch failure comparison.