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

Hive Workflow Improvements #6410

Closed
rswanson opened this issue Feb 5, 2024 · 0 comments
Closed

Hive Workflow Improvements #6410

rswanson opened this issue Feb 5, 2024 · 0 comments
Assignees
Labels
A-meta Changes in the contributor workflow and planning C-enhancement New feature or request C-test A change that impacts how or what we test

Comments

@rswanson
Copy link
Collaborator

rswanson commented Feb 5, 2024

Describe the feature

To further improve the developer experience of the hive testing it would be great if there was automation that could create a new issue in the event that a test that was previously successful starts to fail. It would specifically NOT create an issue if the results do not change between runs. So this means that if a hive test fails once it will generate an issue, and then if it fails on the next days run it will not create a second issue.

Open Questions

  • Should the automation make a comment or something else on subsequent failures? So on a second failure in a row should it comment "It failed again!" (or probably something a bit more useful)
@rswanson rswanson added C-enhancement New feature or request S-needs-triage This issue needs to be labelled labels Feb 5, 2024
@rswanson rswanson self-assigned this Feb 5, 2024
@DaniPopes DaniPopes added C-test A change that impacts how or what we test A-meta Changes in the contributor workflow and planning and removed S-needs-triage This issue needs to be labelled labels Feb 5, 2024
@rswanson rswanson closed this as completed Mar 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-meta Changes in the contributor workflow and planning C-enhancement New feature or request C-test A change that impacts how or what we test
Projects
Archived in project
Development

No branches or pull requests

2 participants