-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Minor
-
Component/s: core
-
2.371
Security2779Test#noXssInHelp() is flaky, according to the build logs: build log on ci.jenkins.io
The first test passes, but the following five fail:
[2022-09-20T02:56:55.267Z] [WARNING] Flakes: [2022-09-20T02:56:55.267Z] [WARNING] Security2779Test.noXssInHelp [2022-09-20T02:56:55.267Z] [INFO] Run 1: PASS [2022-09-20T02:56:55.267Z] [ERROR] Run 2: expected:<0> but was:<1> [2022-09-20T02:56:55.267Z] [ERROR] Run 3: expected:<0> but was:<1> [2022-09-20T02:56:55.267Z] [ERROR] Run 4: expected:<0> but was:<1> [2022-09-20T02:56:55.267Z] [ERROR] Run 5: expected:<0> but was:<1> [2022-09-20T02:56:55.267Z] [ERROR] Run 6: expected:<0> but was:<1>
Improve the test so that it accurately reports the state of the code rather than incorrectly reporting a real failure as a "flaky test". The test is not unreliable. It was correctly identifying a failing condition. The Maven surefire plugin seems to incorrectly classify the test as unreliable.
