Test Failure: com.github.ambry.network.http2.AmbrySendToHttp2AdaptorTest > testServerWrite FAILED
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 298
- Avg merge
- 21h 43m
- Merged PRs (30d)
- 9
Description
```
com.github.ambry.network.http2.AmbrySendToHttp2AdaptorTest > testServerWrite FAILED
java.lang.AssertionError: HeapMemoryLeak: [allocation|deallocation] before test[280|279], after test[281|281] expected:<1> but was:<0>
at org.junit.Assert.fail(Assert.java:91)
at org.junit.Assert.failNotEquals(Assert.java:645)
at org.junit.Assert.assertEquals(Assert.java:126)
at org.junit.Assert.assertEquals(Assert.java:470)
at com.github.ambry.utils.NettyByteBufLeakHelper.afterTest(NettyByteBufLeakHelper.java:103)
at com.github.ambry.network.http2.AmbrySendToHttp2AdaptorTest.after(AmbrySendToHttp2AdaptorTest.java:45)
```
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running AmbrySendToHttp2AdaptorTest.testServerWrite and read its after method together with NettyByteBufLeakHelper.afterTest. Trace the allocation/deallocation count reported by the failure to identify the unmatched buffer lifecycle. Done means the test passes without a HeapMemoryLeak assertion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100