-
Notifications
You must be signed in to change notification settings - Fork 490
add integration test cases on PodGroup in controllers #1797
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
base: main
Are you sure you want to change the base?
Conversation
Summary of ChangesHello @freedown19, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly enhances the integration testing for the PodSet controller by introducing comprehensive test cases for its interaction with Volcano PodGroups. It ensures that PodSets configured with Volcano scheduling strategies correctly provision and manage their associated PodGroups, validating both their specifications and lifecycle statuses. This addition improves the reliability and correctness of the controller's scheduling capabilities. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request adds integration tests for PodSet with Volcano PodGroup functionality. The changes introduce a new test case, validation helpers for PodGroup, and a wrapper extension. However, the new test case is currently broken as it fails to create the PodSet resource and waits for an incorrect number of pods. Furthermore, it incorrectly attempts to validate the PodGroup status, which is outside the control of the component under test in this environment. I've also noted minor typos in error messages within the new validation helpers. My review includes suggestions to fix these issues to ensure the tests are correct and effective.
0ab6080 to
faf0cd5
Compare
Signed-off-by: freedown19 <[email protected]> add podset integration test cases of PodGroup functions Signed-off-by: freedown19 <[email protected]> add podgroup yamls in config dependency dir Signed-off-by: freedown19 <[email protected]> add podgroup yamls in config dependency dir Signed-off-by: freedown19 <[email protected]> add podgroup yamls in config dependency dir Signed-off-by: freedown19 <[email protected]> integration cases of roleset on podgroup Signed-off-by: freedown19 <[email protected]> integration cases of roleset on podgroup Signed-off-by: freedown19 <[email protected]> cleancode fix Signed-off-by: freedown19 <[email protected]> cleancode fix Signed-off-by: freedown19 <[email protected]> cleancode fix Signed-off-by: freedown19 <[email protected]>
8d02717 to
8ab2795
Compare
Signed-off-by: freedown19 <[email protected]>
Signed-off-by: freedown19 <[email protected]>
| @@ -0,0 +1,340 @@ | |||
| --- | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is incorrect, please remove it. We shouldn't just add this CRD.
|
Could you skip PG case for now and support the others first? I'll think about how to modify this when I have time. |
Signed-off-by: freedown19 <[email protected]>
Signed-off-by: freedown19 <[email protected]>
Signed-off-by: freedown19 <[email protected]>
Of course yes. Thanks for your reply and I will skip PG cases for now. If you make any progress, please let me know and I will learn it. |
Pull Request Description
[Please provide a clear and concise description of your changes here]
Related Issues
Resolves: 1784 and #1430
Important: Before submitting, please complete the description above and review the checklist below.
Contribution Guidelines (Expand for Details)
We appreciate your contribution to aibrix! To ensure a smooth review process and maintain high code quality, please adhere to the following guidelines:
Pull Request Title Format
Your PR title should start with one of these prefixes to indicate the nature of the change:
[Bug]: Corrections to existing functionality[CI]: Changes to build process or CI pipeline[Docs]: Updates or additions to documentation[API]: Modifications to aibrix's API or interface[CLI]: Changes or additions to the Command Line Interface[Misc]: For changes not covered above (use sparingly)Note: For changes spanning multiple categories, use multiple prefixes in order of importance.
Submission Checklist
By submitting this PR, you confirm that you've read these guidelines and your changes align with the project's contribution standards.