Test failure: com.github.ambry.frontend.FrontendIntegrationTest > accountApiTest[18]
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 298
- Avg merge
- 21h 43m
- Merged PRs (30d)
- 9
Description
github actions
```
com.github.ambry.frontend.FrontendIntegrationTest > accountApiTest[18] FAILED
java.util.concurrent.ExecutionException: java.io.IOException: Connection reset by peer
at com.github.ambry.router.FutureResult.resultOrThrow(FutureResult.java:113)
at com.github.ambry.router.FutureResult.get(FutureResult.java:99)
at com.github.ambry.frontend.FrontendIntegrationTest.getAccounts(FrontendIntegrationTest.java:820)
at com.github.ambry.frontend.FrontendIntegrationTest.verifyGetAccountsAndContainer(FrontendIntegrationTest.java:774)
at com.github.ambry.frontend.FrontendIntegrationTest.accountApiTest(FrontendIntegrationTest.java:484)
Caused by:
java.io.IOException: Connection reset by peer
```
https://gradle.com/s/yfzrqk3j5gibq
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 FrontendIntegrationTest.accountApiTest, focusing on the failing parameterized case 18. Read getAccounts at FrontendIntegrationTest.java:820, verifyGetAccountsAndContainer at line 774, and accountApiTest at line 484; done means the test no longer fails with a connection reset by peer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100