Skip to content

Conversation

@przemekwitek
Copy link
Contributor

This PR wraps GetDataFrameAnalyticsStatsAction calls in assertBusy so that intermittent search failures do not affect test results.

More insights in the related GH issue linked below.

Relates #55221

@przemekwitek przemekwitek added >test Issues or PRs that are addressing/adding tests :ml Machine learning v8.0.0 v7.8.0 labels Apr 17, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/ml-core (:ml)

Copy link

@droberts195 droberts195 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@przemekwitek
Copy link
Contributor Author

I've just noticed that assertBusy only hides AssertionError, not ElasticsearchException. So this PR as it is, may not fix the issue.

@przemekwitek
Copy link
Contributor Author

run elasticsearch-ci/bwc

@przemekwitek przemekwitek force-pushed the upgrade_mode_assert_busy branch from 88cc194 to 4de370b Compare April 20, 2020 08:46
@przemekwitek
Copy link
Contributor Author

I've just noticed that assertBusy only hides AssertionError, not ElasticsearchException. So this PR as it is, may not fix the issue.

I've fixed that by catching ElasticsearchException and calling Assert.fail (which throws AssertionError making the assertBusy retry).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:ml Machine learning >test Issues or PRs that are addressing/adding tests v7.8.0 v8.0.0-alpha1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants