You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
are almost certainly due to a race condition in CI intake builds involving changes to the analytics in the backend coming into effect before corresponding changes to ES are ready and available to account for them.
Muting these three tests will give CI intake builds a chance to pass.
java.lang.AssertionError:
Expected: a value less than <31500000L>
but: <31762979L> was greater than <31500000L>
at __randomizedtesting.SeedInfo.seed([73F117FB897DC1B:F9E345AC4D4DBBF6]:0)
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:18)
at org.junit.Assert.assertThat(Assert.java:956)
at org.junit.Assert.assertThat(Assert.java:923)
at org.elasticsearch.xpack.ml.integration.AutodetectMemoryLimitIT.testTooManyByAndOverFields(AutodetectMemoryLimitIT.java:176)
java.lang.AssertionError:
Expected: a value less than <116000000L>
but: <116079823L> was greater than <116000000L>
at __randomizedtesting.SeedInfo.seed([73F117FB897DC1B:B2E73A81DE2DCD9E]:0)
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:18)
at org.junit.Assert.assertThat(Assert.java:956)
at org.junit.Assert.assertThat(Assert.java:923)
at org.elasticsearch.xpack.ml.integration.AutodetectMemoryLimitIT.testManyDistinctOverFields(AutodetectMemoryLimitIT.java:226)
java.lang.AssertionError:
Expected: a value less than <31500000L>
but: <32942560L> was greater than <31500000L>
at __randomizedtesting.SeedInfo.seed([73F117FB897DC1B:96A746C3A04BEF2D]:0)
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:18)
at org.junit.Assert.assertThat(Assert.java:956)
at org.junit.Assert.assertThat(Assert.java:923)
at org.elasticsearch.xpack.ml.integration.AutodetectMemoryLimitIT.testTooManyByFields(AutodetectMemoryLimitIT.java:127)
edsavage
added a commit
to edsavage/elasticsearch
that referenced
this issue
May 21, 2019
Re-enable muted tests and accommodate recent backend changes
that result in higher memory usage being reported for a job
at the start of its life-cycle
Fixeselastic#42207
Test failures in:
org.elasticsearch.xpack.ml.integration.AutodetectMemoryLimitIT testManyDistinctOverFields
org.elasticsearch.xpack.ml.integration.AutodetectMemoryLimitIT testTooManyByAndOverFields
org.elasticsearch.xpack.ml.integration.AutodetectMemoryLimitIT testTooManyByFields
are almost certainly due to a race condition in CI intake builds involving changes to the analytics in the backend coming into effect before corresponding changes to ES are ready and available to account for them.
Muting these three tests will give CI intake builds a chance to pass.
relates elastic/ml-cpp#486
relates #42086
The text was updated successfully, but these errors were encountered: