-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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] SingleValueQueryTests testMatchSome {p0=StandardSetup[fieldType=double, multivaluedField=false, empty=false, count=100]} failing #105952
Labels
:Analytics/ES|QL
AKA ESQL
blocker
Team:Analytics
Meta label for analytical engine team (ESQL/Aggs/Geo)
>test-failure
Triaged test failures from CI
Comments
benwtrent
added
:Analytics/ES|QL
AKA ESQL
>test-failure
Triaged test failures from CI
labels
Mar 5, 2024
elasticsearchmachine
added
blocker
Team:Analytics
Meta label for analytical engine team (ESQL/Aggs/Geo)
labels
Mar 5, 2024
Pinging @elastic/es-analytical-engine (Team:Analytics) |
benwtrent
added a commit
to benwtrent/elasticsearch
that referenced
this issue
Mar 5, 2024
benwtrent
added a commit
to benwtrent/elasticsearch
that referenced
this issue
Mar 5, 2024
elasticsearchmachine
pushed a commit
that referenced
this issue
Mar 5, 2024
elasticsearchmachine
pushed a commit
that referenced
this issue
Mar 5, 2024
I believe I fixed this in #105986 but I'll have a look. |
nik9000
added a commit
to nik9000/elasticsearch
that referenced
this issue
Mar 5, 2024
We fixed the test failure in elastic#105986 but this snuck in. Closes elastic#105952
nik9000
added a commit
to nik9000/elasticsearch
that referenced
this issue
Mar 5, 2024
We fixed the test failure in elastic#105986 but this snuck in. Closes elastic#105952
elasticsearchmachine
pushed a commit
that referenced
this issue
Mar 5, 2024
* ESQL: fix single valued query tests (#105986) In some cases the tests for our lucene query that makes sure a field is single-valued was asserting incorrect things about the stats that come from the query. That was failing the test from time to time. This fixes the assertion in those cases. Closes #105918 * ESQL: Reenable svq tests We fixed the test failure in #105986 but this snuck in. Closes #105952
elasticsearchmachine
pushed a commit
that referenced
this issue
Mar 5, 2024
jedrazb
pushed a commit
to jedrazb/elasticsearch
that referenced
this issue
Mar 6, 2024
jedrazb
pushed a commit
to jedrazb/elasticsearch
that referenced
this issue
Mar 6, 2024
We fixed the test failure in elastic#105986 but this snuck in. Closes elastic#105952
gmarouli
pushed a commit
to gmarouli/elasticsearch
that referenced
this issue
Mar 6, 2024
We fixed the test failure in elastic#105986 but this snuck in. Closes elastic#105952
fang-xing-esql
pushed a commit
to fang-xing-esql/Elasticsearch
that referenced
this issue
Mar 8, 2024
fang-xing-esql
pushed a commit
to fang-xing-esql/Elasticsearch
that referenced
this issue
Mar 8, 2024
We fixed the test failure in elastic#105986 but this snuck in. Closes elastic#105952
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Analytics/ES|QL
AKA ESQL
blocker
Team:Analytics
Meta label for analytical engine team (ESQL/Aggs/Geo)
>test-failure
Triaged test failures from CI
Pretty much all of
testMatchSome
fails. I suspect same cause as: #105918Build scan:
https://gradle-enterprise.elastic.co/s/g6ezzkpnkrd42/tests/:x-pack:plugin:esql:test/org.elasticsearch.xpack.esql.querydsl.query.SingleValueQueryTests/testMatchSome%20%7Bp0=StandardSetup%5BfieldType=double,%20multivaluedField=false,%20empty=false,%20count=100%5D%7D
Reproduction line:
Applicable branches:
main, 8.13
Reproduces locally?:
Yes
Failure history:
Failure dashboard for
org.elasticsearch.xpack.esql.querydsl.query.SingleValueQueryTests#testMatchSome {p0=StandardSetup[fieldType=double, multivaluedField=false, empty=false, count=100]}
Failure excerpt:
The text was updated successfully, but these errors were encountered: