Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[CI] InnerHitsIT suite fails #33318

Closed
dnhatn opened this issue Aug 31, 2018 · 1 comment
Closed

[CI] InnerHitsIT suite fails #33318

dnhatn opened this issue Aug 31, 2018 · 1 comment
Assignees
@dnhatn
Labels
:Distributed/Engine Anything around managing Lucene and the Translog in an open shard. >test-failure Triaged test failures from CI

Comments

@dnhatn
Copy link
Member

dnhatn commented Aug 31, 2018

This test suite starts failing after we integrated soft-deletes into Elasticsearch.

I cannot reproduce locally with this command:

./gradlew :server:integTest \
  -Dtests.seed=2A48E284B121F3B \
  -Dtests.class=org.elasticsearch.search.fetch.subphase.InnerHitsIT \
  -Dtests.method="testRandomNested" \
  -Dtests.security.manager=true \
  -Dtests.locale=it-CH \
  -Dtests.timezone=SystemV/MST7MDT \
  -Dcompiler.java=10 \
  -Druntime.java=8

CI instances:
@dnhatn dnhatn added >test-failure Triaged test failures from CI :Distributed/Engine Anything around managing Lucene and the Translog in an open shard. labels Aug 31, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

dnhatn added a commit that referenced this issue Aug 31, 2018
@dnhatn
TEST: Disable soft-deletes in ParentChildTestCase
8703d87 
Tracked at #33318
@dnhatn dnhatn self-assigned this Aug 31, 2018
dnhatn added a commit that referenced this issue Aug 31, 2018
@dnhatn
TEST: Disable soft-deletes in ParentChildTestCase
fc7bf5e 
Tracked at #33318
@dnhatn dnhatn mentioned this issue Sep 2, 2018
Merged
dnhatn added a commit that referenced this issue Sep 3, 2018
@dnhatn
Fix from_range in search_after in changes snapshot (#33335)
24d60c7 
We can have multiple documents in Lucene with the same seq_no for
parent-child documents (or without rollback). In this case, the usage
"lastSeenSeqNo + 1" is an off-by-one error as it may miss some
documents. This error merely affects the `skippedOperations` contract.

See: #33222 (comment)

Closes #33318
dnhatn added a commit that referenced this issue Sep 5, 2018
@dnhatn
Fix from_range in search_after in changes snapshot (#33335)
2a70a0d 
We can have multiple documents in Lucene with the same seq_no for
parent-child documents (or without rollback). In this case, the usage
"lastSeenSeqNo + 1" is an off-by-one error as it may miss some
documents. This error merely affects the `skippedOperations` contract.

See: #33222 (comment)

Closes #33318
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dnhatn dnhatn

Labels
:Distributed/Engine Anything around managing Lucene and the Translog in an open shard. >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dnhatn @elasticmachine