-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Fix not-reported flaky tests #22639
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix not-reported flaky tests #22639
Conversation
Signed-off-by: Michal Hajas <[email protected]>
|
I checked also |
3 flaky tests on run #8589 ↗︎Details:
|
|||||||||||||||||||||||||||||||||
| Test | Artifacts | |
|---|---|---|
| Authentication test > should add a condition |
Output
Screenshots
|
|
realm_settings_events_test.spec.ts • 1 flaky test • chrome
| Test | Artifacts | |
|---|---|---|
| Realm settings events tab tests > Should remove event from event listener |
Output
Screenshots
|
|
realm_settings_general_tab_test.spec.ts • 1 flaky test • chrome
| Test | Artifacts | |
|---|---|---|
| Realm settings general tab tests > Test all general tab switches |
Output
Screenshots
|
|
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings.
Unreported flaky test detectedIf the below flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR. org.keycloak.testsuite.forms.BrowserFlowTest#testAlternativeNonInteractiveExecutorInSubflowKeycloak CI - Forms IT (firefox) org.keycloak.testsuite.model.ConcurrentHashMapStorageTest#testStorageSeparationKeycloak CI - Store Model Tests |
ghost
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unreported flaky test detected, please review
Signed-off-by: Michal Hajas <[email protected]>
Signed-off-by: Michal Hajas <[email protected]>
In the current state, not all flaky tests are reported. The reason for that is that sometimes the failed attempt is reported as a failure and sometimes as an error. The current
upload-flaky-testis looking only for<flakyFailurestring in surefire-reports, however, we need to search also for<flakyError.More info here: https://maven.apache.org/surefire/maven-surefire-plugin/examples/rerun-failing-tests.html#output-flaky-re-run-information-in-test-report-xml