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

FullClusterRestartIT tests and QueryBuilderBWCIT#testQueryBuilderBWC fail #37920

Closed
javanna opened this issue Jan 28, 2019 · 7 comments
Closed
Labels
:Search Foundations/Mapping Index mappings, including merging and defining field types Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch >test-failure Triaged test failures from CI

Comments

@javanna
Copy link
Member

javanna commented Jan 28, 2019

https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+intake/1588/console

These reproduce for me, the error is always along the lines of "The parameter include_type_name should be provided and set to false to be compatible with the next major version":

REPRODUCE WITH: ./gradlew :qa:full-cluster-restart:v6.7.0#oldClusterTestRunner \
  -Dtests.seed=A526EBB7B1417226 \
  -Dtests.class=org.elasticsearch.upgrades.FullClusterRestartIT \
  -Dtests.method="testSearch" \
  -Dtests.security.manager=true \
  -Dtests.locale=hi-IN \
  -Dtests.timezone=America/Managua \
  -Dcompiler.java=11 \
  -Druntime.java=8

REPRODUCE WITH: ./gradlew :qa:full-cluster-restart:v6.7.0#oldClusterTestRunner \
  -Dtests.seed=A526EBB7B1417226 \
  -Dtests.class=org.elasticsearch.upgrades.FullClusterRestartIT \
  -Dtests.method="testNewReplicasWork" \
  -Dtests.security.manager=true \
  -Dtests.locale=hi-IN \
  -Dtests.timezone=America/Managua \
  -Dcompiler.java=11 \
  -Druntime.java=8

REPRODUCE WITH: ./gradlew :qa:full-cluster-restart:v6.7.0#oldClusterTestRunner \
  -Dtests.seed=A526EBB7B1417226 \
  -Dtests.class=org.elasticsearch.upgrades.FullClusterRestartIT \
  -Dtests.method="testShrink" \
  -Dtests.security.manager=true \
  -Dtests.locale=hi-IN \
  -Dtests.timezone=America/Managua \
  -Dcompiler.java=11 \
  -Druntime.java=8

REPRODUCE WITH: ./gradlew :qa:full-cluster-restart:v6.7.0#oldClusterTestRunner \
  -Dtests.seed=A526EBB7B1417226 \
  -Dtests.class=org.elasticsearch.upgrades.FullClusterRestartIT \
  -Dtests.method="testShrinkAfterUpgrade" \
  -Dtests.security.manager=true \
  -Dtests.locale=hi-IN \
  -Dtests.timezone=America/Managua \
  -Dcompiler.java=11 \
  -Druntime.java=8

REPRODUCE WITH: ./gradlew :qa:full-cluster-restart:v6.7.0#oldClusterTestRunner \
  -Dtests.seed=A526EBB7B1417226 \
  -Dtests.class=org.elasticsearch.upgrades.QueryBuilderBWCIT \
  -Dtests.method="testQueryBuilderBWC" \
  -Dtests.security.manager=true \
  -Dtests.locale=it \
  -Dtests.timezone=Australia/Darwin \
  -Dcompiler.java=11 \
  -Druntime.java=8
@javanna javanna added :Search Foundations/Mapping Index mappings, including merging and defining field types >test-failure Triaged test failures from CI labels Jan 28, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-search

@javanna
Copy link
Member Author

javanna commented Jan 28, 2019

I muted these tests.

javanna added a commit that referenced this issue Jan 28, 2019
@DaveCTurner
Copy link
Contributor

I think this might be a consequence of other failures in 6.x presently holding the last good commit back. In particular, 14adf8a is not yet included in the last good commit in 6.x.

@droberts195
Copy link
Contributor

I think this might be a consequence of other failures in 6.x presently holding the last good commit back

I've seen these tests fail in PR builds today and I don't think PR builds use last good commit?

My theory for how this is broken is that #37838 was merged to 6.x at about the same time that #37796 was merged to master. So they both passed all the PR checks with the other absent, but after merging they had to work together and didn't. It's just a theory though, I have no proof...

@javanna
Copy link
Member Author

javanna commented Jan 28, 2019

I've seen it in two PRs in a row as well, which is why I went and muted them straight-away.

@DaveCTurner
Copy link
Contributor

I don't think PR builds use last good commit?

Apologies, yes, this is the case.

@jtibshirani
Copy link
Contributor

Thank you @javanna and @martijnvg for fixing this, and sorry for these failures! I'll take a look at the fixes and may follow-up with a couple tweaks.

jtibshirani added a commit that referenced this issue Feb 13, 2019
…37944)

Instead of using `WarningsHandler.PERMISSIVE`, we only match warnings
that are due to types removal.

This PR also renames `allowTypeRemovalWarnings` to `allowTypesRemovalWarnings`.

Relates to #37920.
jtibshirani added a commit that referenced this issue Feb 13, 2019
…37944)

Instead of using `WarningsHandler.PERMISSIVE`, we only match warnings
that are due to types removal.

This PR also renames `allowTypeRemovalWarnings` to `allowTypesRemovalWarnings`.

Relates to #37920.
jtibshirani added a commit that referenced this issue Feb 13, 2019
…37944)

Instead of using `WarningsHandler.PERMISSIVE`, we only match warnings
that are due to types removal.

This PR also renames `allowTypeRemovalWarnings` to `allowTypesRemovalWarnings`.

Relates to #37920.
@javanna javanna added the Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch label Jul 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Search Foundations/Mapping Index mappings, including merging and defining field types Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

5 participants