[
https://issues.apache.org/jira/browse/KUDU-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17120687#comment-17120687
]
RuiChen commented on KUDU-3131:
-------------------------------
According to the glibc issue history,
[https://sourceware.org/bugzilla/show_bug.cgi?id=23844] , this issue is found
at glibc 2.26, and be fixed in master and backported to 2.29 and 2.28, so the
impacted glibc release should be [2.26, 2.27], huangtianhua, zhaorenhai and I
execute ARM CI test cases on ubuntu 18.04 (with glibc 2.27), that will cause
deadlock because of glibc issue, so we plan to use ubuntu 20.04 (with glibc
2.30) or 16.04 (with glibc 2.23) to instead, that should be OK.
> 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)
