-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
CI: VariableWidthHistogramAggregatorTests#testMultipleSegments #60673
Comments
Pinging @elastic/es-search (:Search/Search) |
Pinging @elastic/es-analytics-geo (:Analytics/Aggregations) |
I couldn't get this to reproduce, either with the reproduction line from the failing build's reproduce line or by running it locally a couple thousand times. I imagine #60683 has changed it. If this comes up again, I'll take another look. But for now I'll close. |
I'm able to reproduce this against a8a34ec with:
|
This happens because we have a test that randomizes stuff pretty hard and it had some assumptions about the shape of the documents that turn out not to be true. Protip: the results are pretty wonky when you only allow a few pieces docs per shard and ask for very few clusters. This should only be a testing problem. Hopefully. |
This test assumed some random bounds that turned out not to hold in some cases. Closes elastic#60673
This test assumed some random bounds that turned out not to hold in some cases. Closes #60673
This test assumed some random bounds that turned out not to hold in some cases. Closes elastic#60673
@nik9000 This happened again in If I get it right, there is no |
I thought that the 7.9 branch was "mostly dead" so we don't backport test fixes. Are we still running them consistently? |
Error Message
java.lang.AssertionError: expected: but was:
Stacktrace
The text was updated successfully, but these errors were encountered: