-
Notifications
You must be signed in to change notification settings - Fork 901
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
TestPerChannelBookieClient.testEpollChannelTcpUserTimeout fails #2787
Comments
@RaulGracia can you please take a look ? |
for reference: |
@eolivelli sure, will allocate some time soon to fix this flaky test. |
@RaulGracia did you have time to take a look ? |
@eolivelli not yet, my plan is to address this one after the release of Pravega 0.10 (going on right now). |
… fails - Fixes apache#2787 - On some Linux systems the value 1234 is rounded to 1236, this patch simply uses 1236 as value in order to prevent failures
BUG REPORT
After we committed c8d4086 I see this test failing very often on DataStax CI, that run the tests against current BookKeeper master, on JDK8.
Describe the bug
This is the error
[ERROR] Failures:
[ERROR] org.apache.bookkeeper.proto.TestPerChannelBookieClient.testEpollChannelTcpUserTimeout
[ERROR] Run 1: TestPerChannelBookieClient.testEpollChannelTcpUserTimeout:337 expected:<1236> but was:<1234>
[ERROR] Run 2: TestPerChannelBookieClient.testEpollChannelTcpUserTimeout:337 expected:<1236> but was:<1234>
[ERROR] Run 3: TestPerChannelBookieClient.testEpollChannelTcpUserTimeout:337 expected:<1236> but was:<1234>
This is the line
c8d4086#diff-271106bdb4f954bd92d6de6e38f2e9dfa542754e611001050350a72bd7a0b9acR338
The text was updated successfully, but these errors were encountered: