Skip to content
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

Closed
eolivelli opened this issue Sep 7, 2021 · 5 comments · Fixed by #2801
Closed

TestPerChannelBookieClient.testEpollChannelTcpUserTimeout fails #2787

eolivelli opened this issue Sep 7, 2021 · 5 comments · Fixed by #2801

Comments

@eolivelli
Copy link
Contributor

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

@eolivelli
Copy link
Contributor Author

@RaulGracia can you please take a look ?
is it possible that Netty adapts the value ?

@eolivelli eolivelli added this to the 4.15.0 milestone Sep 7, 2021
@eolivelli
Copy link
Contributor Author

eolivelli commented Sep 7, 2021

for reference:
[ApacheBookKeeper] $ mvn -s /tmp/settings10138559118398016608.xml -v
Apache Maven 3.6.0
Maven home: /usr/share/maven
Java version: 1.8.0_292, vendor: Private Build, runtime: /usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en, platform encoding: UTF-8
OS name: "linux", version: "4.15.0-64-generic", arch: "amd64", family: "unix"

@RaulGracia
Copy link
Contributor

@eolivelli sure, will allocate some time soon to fix this flaky test.

@eolivelli
Copy link
Contributor Author

@RaulGracia did you have time to take a look ?

@RaulGracia
Copy link
Contributor

@eolivelli not yet, my plan is to address this one after the release of Pravega 0.10 (going on right now).

eolivelli added a commit to eolivelli/bookkeeper that referenced this issue Sep 21, 2021
… 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants