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

[GreenRay] Automated fixing release test failures #34243

Closed
can-anyscale opened this issue Apr 10, 2023 · 4 comments
Closed

[GreenRay] Automated fixing release test failures #34243

can-anyscale opened this issue Apr 10, 2023 · 4 comments
Assignees
Labels
Devprod stale The issue is stale. It will be closed within 7 days unless there are further conversation

Comments

@can-anyscale
Copy link
Collaborator

Capture a list of tasks to:

  • Detect when a core release tests start to fail
  • Classify infra vs application code issue
  • Open issues for repetitive application code issue
  • Bisect and auto-revert blame PRs
@can-anyscale can-anyscale self-assigned this Apr 10, 2023
@can-anyscale can-anyscale changed the title [GreenRay] Processes to Fix Core release test failures [GreenRay] Automated fixing release test failures Apr 12, 2023
@stale
Copy link

stale bot commented Oct 15, 2023

Hi, I'm a bot from the Ray team :)

To help human contributors to focus on more relevant issues, I will automatically add the stale label to issues that have had no activity for more than 4 months.

If there is no further activity in the 14 days, the issue will be closed!

  • If you'd like to keep the issue open, just leave any comment, and the stale label will be removed!
  • If you'd like to get more attention to the issue, please tag one of Ray's contributors.

You can always ask for help on our discussion forum or Ray's public slack channel.

@stale stale bot added the stale The issue is stale. It will be closed within 7 days unless there are further conversation label Oct 15, 2023
@aslonnie
Copy link
Collaborator

aslonnie commented Nov 5, 2023

Bisect and auto-revert blame PRs

do we still plan to do this part?

@can-anyscale
Copy link
Collaborator Author

Yess, we will need to do auto-revert for weekly release

@can-anyscale
Copy link
Collaborator Author

bisect and blame is done; we didn't do auto-revert, the blame rate is manageable by human

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Devprod stale The issue is stale. It will be closed within 7 days unless there are further conversation
Projects
None yet
Development

No branches or pull requests

2 participants