Two tests have been failing in the mixed cluster tests where the mixed cluster contains 7.7 with 7.2 or 7.3:
search.aggregation/10_histogram/date_histogram on range with offsetsearch.aggregation/10_histogram/date_histogram on range
Some example failures are:
But there are other combinations too.
Example repro commands that consistently fail:
./gradlew ':qa:mixed-cluster:v7.2.1#mixedClusterTest' --tests "org.elasticsearch.backwards.MixedClusterClientYamlTestSuiteIT" \
-Dtests.method="test {p0=search.aggregation/10_histogram/date_histogram on range}" \
-Dtests.seed=9966AE98B59516C2 \
-Dtests.security.manager=true \
-Dtests.locale=es-EC \
-Dtests.timezone=Canada/Atlantic \
-Dcompiler.java=13 \
-Druntime.java=11
./gradlew ':qa:mixed-cluster:v7.2.1#mixedClusterTest' --tests "org.elasticsearch.backwards.MixedClusterClientYamlTestSuiteIT" \
-Dtests.method="test {p0=search.aggregation/10_histogram/date_histogram on range with offset}" \
-Dtests.seed=9966AE98B59516C2 \
-Dtests.security.manager=true \
-Dtests.locale=es-EC \
-Dtests.timezone=Canada/Atlantic \
-Dcompiler.java=13 \
-Druntime.java=11
Errors are of the form:
hits.total.value didn't match expected value:
hits.total.value: expected Integer [4] but was Integer [1]
Sometimes the but was is 2 or 3 instead of 1.
Two tests have been failing in the mixed cluster tests where the mixed cluster contains 7.7 with 7.2 or 7.3:
search.aggregation/10_histogram/date_histogram on range with offsetsearch.aggregation/10_histogram/date_histogram on rangeSome example failures are:
But there are other combinations too.
Example repro commands that consistently fail:
Errors are of the form:
Sometimes the
but wasis 2 or 3 instead of 1.