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

QA: rotating node test #842

Closed
4 tasks done
Tracked by #31
sergio-mena opened this issue May 16, 2023 · 2 comments · Fixed by #883
Closed
4 tasks done
Tracked by #31

QA: rotating node test #842

sergio-mena opened this issue May 16, 2023 · 2 comments · Fixed by #883
Assignees
Labels
qa Quality assurance
Milestone

Comments

@sergio-mena
Copy link
Contributor

sergio-mena commented May 16, 2023

Run the rotating node test as specified in RELEASES.md (using the infra existing in qa-infra), fix any found issue, compare with v0.37.0 results. Finally populate the rotating node section of the v0.38.x report.

  • Set up the DO testbed
  • Run the test: loader set up using the saturation point found in the 200 node test
  • Obtain the relevant prometheus plots
    • Compare them to those obtained for v0.37.0
  • Write corresponding section of the QA report

DoD:

  • No showstopper bugs found remain unresolved
  • Rotating node section of the QA report is merged into main and v0.38.x
  • No unacceptable performance regression detected (usually > 10% degradation w.r.t. v0.37.0
@sergio-mena sergio-mena self-assigned this May 16, 2023
@sergio-mena sergio-mena added this to the 2023-Q2 milestone May 16, 2023
@sergio-mena sergio-mena changed the title rotating node QA: rotating node test May 16, 2023
@cason
Copy link
Contributor

cason commented May 17, 2023

@sergio-mena
Copy link
Contributor Author

@cason yes

@sergio-mena sergio-mena added the qa Quality assurance label May 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
qa Quality assurance
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants