Skip to content

[CI] Netty4HttpServerTransportTests testRespondAfterServiceCloseWithServerCancel failing #126745

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
Closed
elasticsearchmachine opened this issue Apr 12, 2025 · 1 comment · Fixed by #126744
Closed

[CI] Netty4HttpServerTransportTests testRespondAfterServiceCloseWithServerCancel failing #126745

elasticsearchmachine opened this issue Apr 12, 2025 · 1 comment · Fixed by #126744
Assignees
@mhl-b
Labels
:Distributed Coordination/Network Http and internode communication implementations low-risk An open issue or test failure that is a low risk to future releases Team:Distributed Coordination Meta label for Distributed Coordination team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented Apr 12, 2025 •
edited
Loading

Build Scans:

Reproduction Line:

gradlew ":modules:transport-netty4:test" --tests "org.elasticsearch.http.netty4.Netty4HttpServerTransportTests.testRespondAfterServiceCloseWithServerCancel" -Dtests.seed=9C479E395E212B79 -Dtests.locale=fur-Latn-IT -Dtests.timezone=SystemV/CST6CDT -Druntime.java=24

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: 
Expected: an empty collection
     but: <[LEAK: ByteBuf.release() was not called before it's garbage-collected. See https://netty.io/wiki/reference-counted-objects.html for more information.
Recent access records: 
#1:
	Hint: Caller of readInbound() will handle the message from this point
	io.netty.buffer.AdvancedLeakAwareCompositeByteBuf.touch(AdvancedLeakAwareCompositeByteBuf.java:36)
	io.netty.handler.codec.http.HttpObjectAggregator$AggregatedFullHttpMessage.touch(HttpObjectAggregator.java:366)
	io.netty.handler.codec.http.HttpObjectAggregator$AggregatedFullHttpRequest.touch(HttpObjectAggregator.java:445)
	io.netty.handler.codec.http.HttpObjectAggregator$AggregatedFullHttpRequest.touch(HttpObjectAggregator.java:396)
	io.netty.channel.embedded.EmbeddedChannel.readInbound(EmbeddedChannel.java:314)
	org.elasticsearch.http.netty4.Netty4HttpHeaderValidatorTests.testWithFlowControlAndAggregator(Netty4HttpHeaderValidatorTests.java:160)
	java.base/jdk.
[truncated]

Issue Reasons:

  • [main] 3 consecutive failures in step windows-2022_checkpart1_platform-support-windows
  • [main] 3 failures in test testRespondAfterServiceCloseWithServerCancel (1.5% fail rate in 194 executions)
  • [main] 3 failures in step windows-2022_checkpart1_platform-support-windows (75.0% fail rate in 4 executions)
  • [main] 3 failures in pipeline elasticsearch-periodic-platform-support (75.0% fail rate in 4 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
@elasticsearchmachine elasticsearchmachine added :Distributed Coordination/Network Http and internode communication implementations >test-failure Triaged test failures from CI needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Distributed Coordination Meta label for Distributed Coordination team labels Apr 12, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination)

@mhl-b mhl-b mentioned this issue Apr 14, 2025
Merged
@mhl-b mhl-b added low-risk An open issue or test failure that is a low risk to future releases and removed needs:risk Requires assignment of a risk label (low, medium, blocker) labels Apr 14, 2025
@mhl-b mhl-b self-assigned this Apr 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mhl-b mhl-b

Labels
:Distributed Coordination/Network Http and internode communication implementations low-risk An open issue or test failure that is a low risk to future releases Team:Distributed Coordination Meta label for Distributed Coordination team >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Release buffers in netty test mhl-b/elasticsearch
2 participants
@mhl-b @elasticsearchmachine