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.

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] TextFieldMapperTests testBlockLoaderFromRowStrideReaderWithSyntheticSource failing #115066

Closed
elasticsearchmachine opened this issue Oct 18, 2024 · 7 comments
Assignees
Labels
low-risk An open issue or test failure that is a low risk to future releases :StorageEngine/Mapping The storage related side of mappings Team:StorageEngine >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented Oct 18, 2024

Build Scans:

Reproduction Line:

./gradlew ":server:test" --tests "org.elasticsearch.index.mapper.TextFieldMapperTests.testBlockLoaderFromColumnReaderWithSyntheticSource" -Dtests.seed=A5C3AE4CEE9FE420 -Dtests.locale=en-BB -Dtests.timezone=America/Argentina/Tucuman -Druntime.java=22

Applicable branches:
8.x

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: expected null, but was:<BlockSourceReader.Bytes[All]>

Issue Reasons:

  • [8.x] 7 failures in test testBlockLoaderFromRowStrideReaderWithSyntheticSource (5.1% fail rate in 138 executions)
  • [8.x] 2 failures in step part1 (9.5% fail rate in 21 executions)
  • [8.x] 5 failures in step part-1 (21.7% fail rate in 23 executions)
  • [8.x] 2 failures in pipeline elasticsearch-intake (9.5% fail rate in 21 executions)
  • [8.x] 5 failures in pipeline elasticsearch-pull-request (25.0% fail rate in 20 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.

@elasticsearchmachine elasticsearchmachine added :Analytics/ES|QL AKA ESQL >test-failure Triaged test failures from CI labels Oct 18, 2024
elasticsearchmachine added a commit that referenced this issue Oct 18, 2024
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 2 consecutive failures in test testBlockLoaderFromRowStrideReaderWithSyntheticSource
  • [main] 2 failures in test testBlockLoaderFromRowStrideReaderWithSyntheticSource (0.9% fail rate in 232 executions)

Build Scans:

@elasticsearchmachine elasticsearchmachine added Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) needs:risk Requires assignment of a risk label (low, medium, blocker) labels Oct 18, 2024
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-analytical-engine (Team:Analytics)

@alex-spies alex-spies added medium-risk An open issue or test failure that is a medium risk to future releases and removed needs:risk Requires assignment of a risk label (low, medium, blocker) labels Oct 18, 2024
@cbuescher
Copy link
Member

Looks related to #115076.

@martijnvg martijnvg self-assigned this Oct 18, 2024
@martijnvg martijnvg added :StorageEngine/Mapping The storage related side of mappings and removed :Analytics/ES|QL AKA ESQL labels Oct 18, 2024
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-storage-engine (Team:StorageEngine)

@elasticsearchmachine elasticsearchmachine removed the Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) label Oct 18, 2024
@martijnvg martijnvg added low-risk An open issue or test failure that is a low risk to future releases and removed medium-risk An open issue or test failure that is a medium risk to future releases labels Oct 18, 2024
@martijnvg
Copy link
Member

Closing in favour of #115076.

lkts pushed a commit to lkts/elasticsearch that referenced this issue Oct 18, 2024
@elasticsearchmachine
Copy link
Collaborator Author

This issue is being re-opened because the referenced test still exists in muted-tests.yml, so it is still muted.

Please check and unmute the test if it can be unmuted.

In the future, automation will automatically re-open issues whenever they are closed without unmuting the test first.

Reach out in #es-delivery or tag the delivery team if you have an issue.

cc @martijnvg

@martijnvg
Copy link
Member

Fixed and unmuted via #115114

georgewallace pushed a commit to georgewallace/elasticsearch that referenced this issue Oct 25, 2024
jfreden pushed a commit to jfreden/elasticsearch that referenced this issue Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
low-risk An open issue or test failure that is a low risk to future releases :StorageEngine/Mapping The storage related side of mappings Team:StorageEngine >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

4 participants