-
Notifications
You must be signed in to change notification settings - Fork 25.2k
[CI] FiltersAggregatorTests.testMatchNoneTopLevel failing on master #74677
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
Comments
Pinging @elastic/es-analytics-geo (Team:Analytics) |
A different test in the same test suite failed today with a similar error: https://gradle-enterprise.elastic.co/s/vypetlhquslnk
|
@nik9000 if you happen to look at this class, there are many CI failures for the following test in the past 7 days:
|
Sorry I hadn't picked this up yesterday. I'd lost it in the shuffle between morning emails and starting work for real. I'll dig now. Sorry for the noise! |
The tests for the debugging information in the filters aggregation where too specific for the kind of randomization we run with. They asserted that the indices contained only a single segment which is *usually* true, but our test randomization framework sometimes emit many segmented indices, just to exercise the code. That's a good thing. But the tests had a wrong assertion. This swaps the assertion from `equalTo(1)` to `greaterThanOrEqualTo(1)`. Closes elastic#74677
Well that wasn't too bad! I was asserting that the indices I was testing with only had a single segment. By accident. Changed it to |
The tests for the debugging information in the filters aggregation where too specific for the kind of randomization we run with. They asserted that the indices contained only a single segment which is *usually* true, but our test randomization framework sometimes emit many segmented indices, just to exercise the code. That's a good thing. But the tests had a wrong assertion. This swaps the assertion from `equalTo(1)` to `greaterThanOrEqualTo(1)`. Closes #74677
The tests for the debugging information in the filters aggregation where too specific for the kind of randomization we run with. They asserted that the indices contained only a single segment which is *usually* true, but our test randomization framework sometimes emit many segmented indices, just to exercise the code. That's a good thing. But the tests had a wrong assertion. This swaps the assertion from `equalTo(1)` to `greaterThanOrEqualTo(1)`. Closes elastic#74677
The tests for the debugging information in the filters aggregation where too specific for the kind of randomization we run with. They asserted that the indices contained only a single segment which is *usually* true, but our test randomization framework sometimes emit many segmented indices, just to exercise the code. That's a good thing. But the tests had a wrong assertion. This swaps the assertion from `equalTo(1)` to `greaterThanOrEqualTo(1)`. Closes elastic#74677
The tests for the debugging information in the filters aggregation where too specific for the kind of randomization we run with. They asserted that the indices contained only a single segment which is *usually* true, but our test randomization framework sometimes emit many segmented indices, just to exercise the code. That's a good thing. But the tests had a wrong assertion. This swaps the assertion from `equalTo(1)` to `greaterThanOrEqualTo(1)`. Closes #74677 Co-authored-by: Elastic Machine <[email protected]>
The tests for the debugging information in the filters aggregation where too specific for the kind of randomization we run with. They asserted that the indices contained only a single segment which is *usually* true, but our test randomization framework sometimes emit many segmented indices, just to exercise the code. That's a good thing. But the tests had a wrong assertion. This swaps the assertion from `equalTo(1)` to `greaterThanOrEqualTo(1)`. Closes #74677 Co-authored-by: Elastic Machine <[email protected]>
Thanks Nik! |
Uh oh!
There was an error while loading. Please reload this page.
This happend on a local run but seems reproducable on master
Build scan:
Edit: this is from a CI test failure on Sunday that looks similar
https://gradle-enterprise.elastic.co/s/wphgk3nxj73jg
Repro line:
Reproduces locally?:
yes
Applicable branches:
master
Failure history:
Failure excerpt:
The text was updated successfully, but these errors were encountered: