You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "RuiChen (Jira)" <ji...@apache.org> on 2020/06/01 01:30:00 UTC
[jira] [Comment Edited] (KUDU-3131) test rw_mutex-test hangs
sometimes if build_type is release
[ https://issues.apache.org/jira/browse/KUDU-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17120061#comment-17120061 ]
RuiChen edited comment on KUDU-3131 at 6/1/20, 1:29 AM:
--------------------------------------------------------
Add some info, I test the case in my local Ubuntu 16.04 docker container with glibc 2.23, run 1000 times, no hang happen. I think the issue is related with glibc issue showed by huangtianhua, looks it impact glibc [2.26, 2.28), see my local env info in following:
{code:java}
root@8bb63502a8e9:/kudu/build/release/bin# cat /etc/issue Ubuntu 16.04.6 LTS \n \l
root@8bb63502a8e9:/kudu/build/release# uname -a Linux 8bb63502a8e9 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:03:46 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux
root@8bb63502a8e9:/kudu/build/release/bin# dpkg -l | grep libc-bin ii libc-bin 2.23-0ubuntu11 arm64 GNU C Library: Binaries
.....
Repeating all tests (iteration 999) . . . Note: Google Test filter = Priorities/RWMutexTest.TestDeadlocks/0 [==========] Running 1 test from 1 test case. [----------] Global test environment set-up. [----------] 1 test from Priorities/RWMutexTest [ RUN ] Priorities/RWMutexTest.TestDeadlocks/0 I0530 01:45:08.035390 25204 rw_mutex-test.cc:107] Number of writes: 92815 I0530 01:45:08.035414 25204 rw_mutex-test.cc:108] Number of reads: 1876317 [ OK ] Priorities/RWMutexTest.TestDeadlocks/0 (1001 ms) [----------] 1 test from Priorities/RWMutexTest (1001 ms total) [----------] Global test environment tear-down [==========] 1 test from 1 test case ran. (1001 ms total) [ PASSED ] 1 test. Repeating all tests (iteration 1000) . . . Note: Google Test filter = Priorities/RWMutexTest.TestDeadlocks/0 [==========] Running 1 test from 1 test case. [----------] Global test environment set-up. [----------] 1 test from Priorities/RWMutexTest [ RUN ] Priorities/RWMutexTest.TestDeadlocks/0 I0530 01:45:09.036151 25204 rw_mutex-test.cc:107] Number of writes: 57396 I0530 01:45:09.036180 25204 rw_mutex-test.cc:108] Number of reads: 1275667 [ OK ] Priorities/RWMutexTest.TestDeadlocks/0 (1001 ms) [----------] 1 test from Priorities/RWMutexTest (1001 ms total) [----------] Globaltestenvironmenttear-down [==========] 1testfrom1testcaseran.(1001mstotal) [ PASSED ] 1test. root@8bb63502a8e9:/kudu/build/release/bin#ll{code}
was (Author: ruichen):
Add some info, I test the case in my local Ubuntu 16.04 docker container with glibc 2.23, run 1000 times, no hang happen. I think the issue is related with glibc issue showed by huangtianhua, looks it impact glibc [2.26, 2.30), see my local env info in following:
{code:java}
root@8bb63502a8e9:/kudu/build/release/bin# cat /etc/issue Ubuntu 16.04.6 LTS \n \l
root@8bb63502a8e9:/kudu/build/release# uname -a Linux 8bb63502a8e9 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:03:46 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux
root@8bb63502a8e9:/kudu/build/release/bin# dpkg -l | grep libc-bin ii libc-bin 2.23-0ubuntu11 arm64 GNU C Library: Binaries
.....
Repeating all tests (iteration 999) . . . Note: Google Test filter = Priorities/RWMutexTest.TestDeadlocks/0 [==========] Running 1 test from 1 test case. [----------] Global test environment set-up. [----------] 1 test from Priorities/RWMutexTest [ RUN ] Priorities/RWMutexTest.TestDeadlocks/0 I0530 01:45:08.035390 25204 rw_mutex-test.cc:107] Number of writes: 92815 I0530 01:45:08.035414 25204 rw_mutex-test.cc:108] Number of reads: 1876317 [ OK ] Priorities/RWMutexTest.TestDeadlocks/0 (1001 ms) [----------] 1 test from Priorities/RWMutexTest (1001 ms total) [----------] Global test environment tear-down [==========] 1 test from 1 test case ran. (1001 ms total) [ PASSED ] 1 test. Repeating all tests (iteration 1000) . . . Note: Google Test filter = Priorities/RWMutexTest.TestDeadlocks/0 [==========] Running 1 test from 1 test case. [----------] Global test environment set-up. [----------] 1 test from Priorities/RWMutexTest [ RUN ] Priorities/RWMutexTest.TestDeadlocks/0 I0530 01:45:09.036151 25204 rw_mutex-test.cc:107] Number of writes: 57396 I0530 01:45:09.036180 25204 rw_mutex-test.cc:108] Number of reads: 1275667 [ OK ] Priorities/RWMutexTest.TestDeadlocks/0 (1001 ms) [----------] 1 test from Priorities/RWMutexTest (1001 ms total) [----------] Globaltestenvironmenttear-down [==========] 1testfrom1testcaseran.(1001mstotal) [ PASSED ] 1test. root@8bb63502a8e9:/kudu/build/release/bin#ll{code}
> test rw_mutex-test hangs sometimes if build_type is release
> -----------------------------------------------------------
>
> Key: KUDU-3131
> URL: https://issues.apache.org/jira/browse/KUDU-3131
> Project: Kudu
> Issue Type: Sub-task
> Reporter: huangtianhua
> Priority: Major
>
> Built and test kudu on aarch64, in release mode there is a test hangs sometimes(maybe a deadlock?) the console out as following:
> [==========] Running 2 tests from 1 test case.
> [----------] Global test environment set-up.
> [----------] 2 tests from Priorities/RWMutexTest
> [ RUN ] Priorities/RWMutexTest.TestDeadlocks/0
> And seems it's ok in debug mode.
> Now only this one test failed sometimes on aarch64, [~aserbin] [~adar] would you please have a look for this? Or give some suggestion to us, thanks very much.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)