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

Fix flaky test getAllInstances - clean up added instances #2879

Merged
merged 1 commit into from
Aug 9, 2024

Conversation

GrantPSpencer
Copy link
Contributor

Issues

  • My PR addresses the following Helix issues and references them in the PR description:

#2836
testGetAllInstances flaky in CI

Description

  • Here are some details about my PR, including screenshots of any UI changes:

Test failing due to comparison of in memory instance map vs response from getAllInstances. getAllInstances "instances" value is built from the instance configs in the cluster.
testInstancesAccessor and testPerInstanceAccessor both modify the same cluster - TestCluster_4
updateInstance in testPerInstanceAccessor adds an instance config but does not remove it. This may lead to the failure in testGetAllInstances because the cluster has an instance config added but the in memory map of _instancesMap does not have an instance added as well

Looking at the logs of previously failed runs vs successful runs. Successful runs have testInstancesAcessor run before testPerInstanceAccessor. Failed runs are the reverse

Tests

  • The following tests are written for this issue:

N/A

  • The following is the result of the "mvn test" command on the appropriate module:
$ mvn test -o -pl=helix-rest
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  05:40 min
[INFO] Finished at: 2024-08-08T21:19:20-07:00
[INFO] ------------------------------------------------------------------------

Commits

  • My commits all reference appropriate Apache Helix GitHub issues in their subject lines. In addition, my commits follow the guidelines from "How to write a good git commit message":
    1. Subject is separated from body by a blank line
    2. Subject is limited to 50 characters (not including Jira issue reference)
    3. Subject does not end with a period
    4. Subject uses the imperative mood ("add", not "adding")
    5. Body wraps at 72 characters
    6. Body explains "what" and "why", not "how"

Code Quality

  • My diff has been formatted using helix-style.xml
    (helix-style-intellij.xml if IntelliJ IDE is used)

@GrantPSpencer
Copy link
Contributor Author

Pull request approved @junkaixue, @zpinto
Commit message: Fix flaky test getAllInstances - clean up added instances

@junkaixue junkaixue merged commit 5188f79 into apache:master Aug 9, 2024
2 checks passed
htin1 pushed a commit to htin1/helix that referenced this pull request Aug 23, 2024
Fix flaky test getAllInstances - clean up added instances
htin1 pushed a commit to htin1/helix that referenced this pull request Aug 29, 2024
Fix flaky test getAllInstances - clean up added instances
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.

3 participants