-
Notifications
You must be signed in to change notification settings - Fork 275
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
Fix misbehaving tests #295
Comments
Tagged with newbie. Might be useful for someone new to debug the tests and learn the code. |
@sriramsub Hey, I am exploring the testRollingIndex test, can you give me the scenario for reproducing the test failure? |
@greplog This is indeed a good starter issue to look into. The test fails intermittently. @cgtz may have more idea about how to reproduce it. But when it does fail, we see the following:
This is most likely an issue with the test being incorrect. Either way, I would recommend starting with these steps:
Feel free to ask us about anything at [email protected]. |
@pnarayanan Thanks for the heads up and error log, as you suggested, I am going through the code, and will try to reproduce and fix it. |
Hi @greplog! To help with reproducing this bug, after uncommenting the test you want to target, try running the tests in a loop using this bash command:
|
Hi all, there are other tests also failing in the current system like DiskTest.testDiskSoftState Plus, can somebody help me with the difference in task unitTest and test, I am assuming test is running integration plus unit tests, while unitTest is running only unit tests. stacktrace of other failing tests 26 tests completed, 1 failed |
Hi @greplog, thanks for finding this! What type of system did it fail on? I can add it to the list. Regarding the test and unitTest targets, you are correct. test runs the server integration tests as well. We set it up this way so that the build target will just run the unit test suite but test will run both. |
Hi @cgtz |
attn: @nsivabalan |
(Edits by @vgkholla to delete tests that are no longer relevant)
The following tests were failing intermittently or hanging and were commented out in PR #294. This ticket tracks their fixes.
In BlockingChannelConnectionPoolTest:
In SimpleByteBufferPoolTest:
The text was updated successfully, but these errors were encountered: