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

Test failure - invalid query syntax in new yml test #24734

Closed
markharwood opened this issue May 17, 2017 · 2 comments
Closed

Test failure - invalid query syntax in new yml test #24734

markharwood opened this issue May 17, 2017 · 2 comments
Assignees
Labels
>test Issues or PRs that are addressing/adding tests >test-failure Triaged test failures from CI

Comments

@markharwood
Copy link
Contributor

Bad match query syntax: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+multijob-intake/1270/console

Reproduces

REPRODUCE WITH: gradle :modules:analysis-common:integTestRunner -Dtests.seed=1045551E25D9DAC7 -Dtests.class=org.elasticsearch.analysis.common.CommonAnalysisClientYamlTestSuiteIT -Dtests.method="test {yaml=search.query/10_match/match query with stacked stems}" -Dtests.security.manager=true -Dtests.locale=sq-AL -Dtests.timezone=Asia/Ujung_Pandang
	   "type" : "parsing_exception",
	   "reason" : "[match] query doesn't support multiple fields, found [text] and [operator]",
	   "stack_trace" : "ParsingException[[match] query doesn't support multiple fields, found [text] and [operator]]

Looks like bad query syntax as part of this commit:

@markharwood markharwood added >test-failure Triaged test failures from CI >test Issues or PRs that are addressing/adding tests labels May 17, 2017
@nik9000
Copy link
Member

nik9000 commented May 17, 2017 via email

@nik9000
Copy link
Member

nik9000 commented May 17, 2017

Or not. I found some time this morning. These tests were only half written as is my usual test process. I half write them, let them fail, and fix them. But they didn't run so they didn't fail. I found the cause and I'll open a followup later today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>test Issues or PRs that are addressing/adding tests >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

2 participants