Skip to content
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

Detailed test report for github actions #480

Open
amitgalitz opened this issue Mar 31, 2022 · 0 comments
Open

Detailed test report for github actions #480

amitgalitz opened this issue Mar 31, 2022 · 0 comments
Labels
CCI College Contributor Initiative enhancement New feature or request good first issue Good for newcomers infra Changes to infrastructure, testing, CI/CD, pipelines, etc.

Comments

@amitgalitz
Copy link
Member

Is your feature request related to a problem? Please describe.
After adding gradle-retry to our CI workflow it can lead to some flaky tests never being addressed. Flaky tests will still be displayed in our github action logs even if they pass on retry, however, going through such logs can be pretty messy and time consuming.

Describe the solution you'd like
I propose implementing a similar workflow as seen in this PR in opensearch-core where a nicely formatted CI report is produced at the end of the workflow to easily view if any flaky tests occur

@amitgalitz amitgalitz added enhancement New feature or request good first issue Good for newcomers infra Changes to infrastructure, testing, CI/CD, pipelines, etc. labels Mar 31, 2022
@amitgalitz amitgalitz added the CCI College Contributor Initiative label May 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CCI College Contributor Initiative enhancement New feature or request good first issue Good for newcomers infra Changes to infrastructure, testing, CI/CD, pipelines, etc.
Projects
None yet
Development

No branches or pull requests

1 participant