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

Improve flakiness reporting by storing flaky run report with failed test name and failure message #1335

Merged

Conversation

michalvavrik
Copy link
Member

@michalvavrik michalvavrik commented Sep 24, 2024

Summary

This is the first step to improve flakiness reporting. I need to have the file that we can inspect. Later I can experiment on commenting etc..

Tested here (in the first run): quarkus-qe/quarkus-test-suite#2045

Please check the relevant options

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Dependency update
  • Refactoring
  • Release (follows conventions described in the RELEASE.md)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • This change requires a documentation update
  • This change requires execution against OCP (use run tests phrase in comment)

Checklist:

  • Example scenarios has been updated / added
  • Methods and classes used in PR scenarios are meaningful
  • Commits are well encapsulated and follow the best practices

Copy link
Member

@mjurc mjurc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks

@michalvavrik michalvavrik merged commit 1e563da into quarkus-qe:main Sep 24, 2024
8 checks passed
@michalvavrik michalvavrik deleted the feature/improve-flakiness-reporting branch September 24, 2024 19:15
@michalvavrik michalvavrik mentioned this pull request Sep 25, 2024
12 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants