-
Notifications
You must be signed in to change notification settings - Fork 25.2k
[CI] SmokeTestMultiNodeClientYamlTestSuiteIT class failing #118955
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
Comments
This has been muted on branch main Mute Reasons:
Build Scans: |
…eIT org.elasticsearch.smoketest.SmokeTestMultiNodeClientYamlTestSuiteIT #118955
Pinging @elastic/es-search-relevance (Team:Search Relevance) |
…eIT org.elasticsearch.smoketest.SmokeTestMultiNodeClientYamlTestSuiteIT elastic#118955
This is a pretty nasty failure. From what I can tell, a node crashed due to an unhandled assertion: The assertion tripped was added here: #114618 relabeling to those teams and marking as a blocker as this whole suite is muted now.
|
/cc @jimczi ^ |
Pinging @elastic/es-storage-engine (Team:StorageEngine) |
Pinging @elastic/es-distributed-indexing (Team:Distributed Indexing) |
I think the immediate reason this started to fail is because of a yaml test that I added via #118924. |
I'm not yet able to figure out why this fails or reproduce. However I'm confident that it is caused by a test that was added in the mentioned PR. So I think we can just mute that test instead of the whole suite: #118989 |
In case of synthetic recovery source the mapping is empty. Closes elastic#118955
In case of synthetic recovery source the mapping is empty. Closes elastic#118955
) In case of synthetic recovery source when the mapping is empty. A test that reproduces failure in #118955 consistently with a potential fix. `MapperService#updateMapping(...)` doesn't set the mapper field if a mapping has no fields, which is what is used in InternalEngine#newChangesSnapshot(...) . This happens when `newMappingMetadata` variable in `MapperService updateMapping(...)` is `null`. Causing an assertion to trip. This change adjusts that assertion to handle an empty index. Closes #118955
…tic#118996) In case of synthetic recovery source when the mapping is empty. A test that reproduces failure in elastic#118955 consistently with a potential fix. `MapperService#updateMapping(...)` doesn't set the mapper field if a mapping has no fields, which is what is used in InternalEngine#newChangesSnapshot(...) . This happens when `newMappingMetadata` variable in `MapperService updateMapping(...)` is `null`. Causing an assertion to trip. This change adjusts that assertion to handle an empty index. Closes elastic#118955
…eIT org.elasticsearch.smoketest.SmokeTestMultiNodeClientYamlTestSuiteIT #118955
This has been muted on branch 8.x Mute Reasons:
Build Scans:
|
…#119089) Backport of #118996 to 8.x branch. In case of synthetic recovery source when the mapping is empty. A test that reproduces failure in #118955 consistently with a potential fix. `MapperService#updateMapping(...)` doesn't set the mapper field if a mapping has no fields, which is what is used in InternalEngine#newChangesSnapshot(...) . This happens when `newMappingMetadata` variable in `MapperService updateMapping(...)` is `null`. Causing an assertion to trip. This change adjusts that assertion to handle an empty index. Closes #118955
Re-opening of this issue is fixed via #119089. The test got muted before that PR was merged. |
…eIT org.elasticsearch.smoketest.SmokeTestMultiNodeClientYamlTestSuiteIT elastic#118955
…tic#118996) In case of synthetic recovery source when the mapping is empty. A test that reproduces failure in elastic#118955 consistently with a potential fix. `MapperService#updateMapping(...)` doesn't set the mapper field if a mapping has no fields, which is what is used in InternalEngine#newChangesSnapshot(...) . This happens when `newMappingMetadata` variable in `MapperService updateMapping(...)` is `null`. Causing an assertion to trip. This change adjusts that assertion to handle an empty index. Closes elastic#118955
@martijnvg in main
This is still muted. |
Ah, I see that this is now a separate issue. LOL, I will close this one and reopen the other! |
Build Scans:
Reproduction Line:
Applicable branches:
main
Reproduces locally?:
N/A
Failure History:
See dashboard
Failure Message:
Issue Reasons:
Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
The text was updated successfully, but these errors were encountered: