Skip to content

[CI] XPackRestIT "analytics/top_metrics/sort by string script fails" failure #52409

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

Closed
astefan opened this issue Feb 17, 2020 · 9 comments · Fixed by #52575
Closed

[CI] XPackRestIT "analytics/top_metrics/sort by string script fails" failure #52409

astefan opened this issue Feb 17, 2020 · 9 comments · Fixed by #52575
Labels
:Analytics/Aggregations Aggregations >test-failure Triaged test failures from CI

Comments

@astefan
Copy link
Contributor

astefan commented Feb 17, 2020

https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.x+multijob-unix-compatibility/os=oraclelinux-7&&immutable/574/console

02:31:08 org.elasticsearch.xpack.test.rest.XPackRestIT > test {p0=analytics/top_metrics/sort by string script fails} FAILED
02:31:08     java.lang.AssertionError: Failure at [analytics/top_metrics:247]: expected [400] status code but api [search] returned [200 OK] [{"took":8,"timed_out":false,"_shards":{"total":2,"successful":1,"skipped":0,"failed":1,"failures":[{"shard":0,"index":"test","node":"gtl65pvDSVSvSoO1viU9Lg","reason":{"type":"illegal_argument_exception","reason":"error building sort for [_script]: script sorting only supported on [numeric] scripts but was [string]"}}]},"hits":{"total":{"value":0,"relation":"eq"},"max_score":null,"hits":[]},"aggregations":{"tm":{"top":[]}}}]
02:31:08         at __randomizedtesting.SeedInfo.seed([6ECA51725C63A9D5:E69E6EA8F29FC42D]:0)
02:31:08         at org.elasticsearch.test.rest.yaml.ESClientYamlSuiteTestCase.executeSection(ESClientYamlSuiteTestCase.java:405)
02:31:08         at org.elasticsearch.test.rest.yaml.ESClientYamlSuiteTestCase.test(ESClientYamlSuiteTestCase.java:382)
02:31:08         at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)

Couldn't repro, though :-(.

@astefan astefan added :Analytics/Aggregations Aggregations >test-failure Triaged test failures from CI labels Feb 17, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-analytics-geo (:Analytics/Aggregations)

@henningandersen
Copy link
Contributor

Another failure in master here:
https://gradle-enterprise.elastic.co/s/muy4t6spxrake

Looks like the index somehow got created with 2 shards.

@henningandersen
Copy link
Contributor

This master failure looks similar, but is for another test case: p0=analytics/top_metrics/sort by keyword field fails
https://gradle-enterprise.elastic.co/s/6expjc2t4e6rs/tests/fcijb24gqtmnc-q63yzuzm4b2wi
Looks like the index also got two shards in this case:

        "successful" : 1,
        "skipped" : 0,
        "failed" : 1,

@henningandersen
Copy link
Contributor

Notice that an index template "global" is randomly added, causing the indices to have two shards.

@nik9000 I noticed this is a new test, maybe you can take a look? skip features: default_shards might do the trick here?

henningandersen added a commit to henningandersen/elasticsearch that referenced this issue Feb 18, 2020
These tests fails when the global template is added, which changes
number_of_shards to 2.

Relates elastic#52409 and elastic#52418
henningandersen added a commit that referenced this issue Feb 18, 2020
These tests fails when the global template is added, which changes
number_of_shards to 2.

Relates #52409 and #52418
henningandersen added a commit that referenced this issue Feb 18, 2020
These tests fails when the global template is added, which changes
number_of_shards to 2.

Relates #52409 and #52418
sbourke pushed a commit to sbourke/elasticsearch that referenced this issue Feb 19, 2020
These tests fails when the global template is added, which changes
number_of_shards to 2.

Relates elastic#52409 and elastic#52418
@nik9000
Copy link
Member

nik9000 commented Feb 20, 2020

Fixed in #52516.

@nik9000
Copy link
Member

nik9000 commented Feb 21, 2020

I had my wires crossed. This wasn't fixed.

@markharwood
Copy link
Contributor

I might just have hit this in a PR build based off master abeb837 which has the number of shards fix. Didn't reproduce locally.

@nik9000
Copy link
Member

nik9000 commented Feb 25, 2020

I might just have hit this in a PR build based off master abeb837 which has the number of shards fix. Didn't reproduce locally.

I'll push some even more paranoid clamping on the test to see if that fixes it....

@nik9000
Copy link
Member

nik9000 commented Feb 25, 2020

More paranoia: 0a4c5e0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Analytics/Aggregations Aggregations >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants