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 AggregationsTests.testFromXContent #5285

Merged
merged 1 commit into from
Nov 17, 2022
Merged

Fix flaky test AggregationsTests.testFromXContent #5285

merged 1 commit into from
Nov 17, 2022

Conversation

adnapibar
Copy link
Contributor

Description

Based on the seed, the recursive createTestInstance method generates too many aggregations resulting in an exception. This change reduces the number of generated aggregations.

Issues Resolved

#4969

Check List

  • New functionality includes testing.
    • All tests pass
  • New functionality has been documented.
    • New functionality has javadoc added
  • Commits are signed per the DCO using --signoff
  • Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Signed-off-by: Rabi Panda adnapibar@gmail.com

Based on the seed, the recursive createTestInstance method generates too many aggregations resulting in an exception. This change reduces the number of generated aggregations.

Signed-off-by: Rabi Panda <adnapibar@gmail.com>
@github-actions
Copy link
Contributor

Gradle Check (Jenkins) Run Completed with:

  • RESULT: UNSTABLE ❕
  • FLAKY TEST FAILURES:
    The following tests failed but succeeded upon retry:
      1 org.opensearch.index.ShardIndexingPressureConcurrentExecutionTests.testCoordinatingPrimaryThreadedUpdateToShardLimitsAndRejections

@andrross
Copy link
Member

Is this usage of createTestInstance() susceptible to the same problem?

@adnapibar
Copy link
Contributor Author

adnapibar commented Nov 17, 2022

Is this usage of createTestInstance() susceptible to the same problem?

I don't think so, the problem with this issue is that the XContentParser fails given this large generated aggregations instance. On another look, it maybe the case, let me test it

@adnapibar
Copy link
Contributor Author

Is this usage of createTestInstance() susceptible to the same problem?

I don't think so, the problem with this issue is that the XContentParser fails given this large generated aggregations instance. On another look, it maybe the case, let me test it

This test doesn't fail for too many aggregations

@andrross andrross merged commit 1bb29e7 into opensearch-project:main Nov 17, 2022
@andrross andrross added the backport 2.x Backport to 2.x branch label Nov 17, 2022
opensearch-trigger-bot bot pushed a commit that referenced this pull request Nov 17, 2022
Based on the seed, the recursive createTestInstance method generates too many aggregations resulting in an exception. This change reduces the number of generated aggregations.

Signed-off-by: Rabi Panda <adnapibar@gmail.com>
(cherry picked from commit 1bb29e7)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
dblock pushed a commit that referenced this pull request Nov 17, 2022
Based on the seed, the recursive createTestInstance method generates too many aggregations resulting in an exception. This change reduces the number of generated aggregations.

Signed-off-by: Rabi Panda <adnapibar@gmail.com>
(cherry picked from commit 1bb29e7)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

Signed-off-by: Rabi Panda <adnapibar@gmail.com>
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport 2.x Backport to 2.x branch skip-changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants