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

[ML] Unmute BWC tests and fix version after backport of #50553 #50599

Conversation

dimitris-athanasiou
Copy link
Contributor

Relates #50553

@elasticmachine
Copy link
Collaborator

Pinging @elastic/ml-core (:ml)

@dimitris-athanasiou
Copy link
Contributor Author

run elasticsearch-ci/2

@@ -40,7 +40,7 @@ private DeleteDataFrameAnalyticsAction() {
public Request(StreamInput in) throws IOException {
super(in);
id = in.readString();
if (in.getVersion().onOrAfter(Version.CURRENT)) {
if (in.getVersion().onOrAfter(Version.V_8_0_0)) {
Copy link
Member

Choose a reason for hiding this comment

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

Since #50589 is merged, shouldn't the version be V_7_6_0?

Copy link
Member

Choose a reason for hiding this comment

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

since BWC has passed with the version being wrong, I am guessing we don't have a BWC test that deletes analytics jobs do we?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ah, 🤦‍♂

Indeed. I'll add one that creates and deletes a job in the mixed cluster.

@dimitris-athanasiou dimitris-athanasiou merged commit 0dc4b31 into elastic:master Jan 3, 2020
@dimitris-athanasiou dimitris-athanasiou deleted the unmute-bwc-tests-after-backport-50553 branch January 3, 2020 14:44
SivagurunathanV pushed a commit to SivagurunathanV/elasticsearch that referenced this pull request Jan 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants