[
https://issues.apache.org/jira/browse/KUDU-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17077559#comment-17077559
]
Adar Dembo commented on KUDU-3007:
----------------------------------
Thanks for doing this amazing work. Looks like we're almost there!
bq. For the LINT and IWYU testing type, it is easy to fix the issues occurs on
ARM, but it is strange that there are several failures of IWYU doesn't look
like relate with ARM and didn't occur in Jenkin CI. details can be find in
"iwyu" directory of above testing results link.
IWYU's recommendations are based on the code that it parses. Since there is
aarch64-specific code that other platforms never compile, it's natural that
running IWYU on aarch64 may yield different recommendations.
To handle that, we add {{// IWYU pragma: keep}} comments alongside the
platform-specific recommendations so that IWYU won't remove them. [This
page|https://github.com/include-what-you-use/include-what-you-use/blob/master/docs/IWYUPragmas.md]
has more details on how IWYU pragmas work.
bq. For DEBUG and RELEASE testing types, we have made many changes in the patch
and the building process are OK now, and >99% test cases can pass now, but
current there still have random 1~3 test case failures every time, we are still
debuging but hard to find explict root cause. more details can be find in the
"debug" and "release" directories of above testing results link.
I took a quick look. In the latest DEBUG run there's a [SIGSEGV in
linked_list-test|http://80.158.17.129/logs/8/8/aa7f8a35bafe7b0e6bd1e6793470c8b4d8aaa14a/check/kudu-build-test-aarch64-in-docker/e6e529b/test_results/debug/test-logs/linked_list-test.txt.gz]
that's kinda weird. Has anyone debugged that yet? The debug-util-test failure
I think is already covered in KUDU-3096.
bq. For ASAN and TSAN testing types, we have struggled a while, but it looks
like there are some problems about TSAN/ASAN support on ARM, we have asked in
https://github.com/google/sanitizers/issues/1208 and will continue to dig more.
Cool, keep us posted. For now we can temporarily enable those with static
linking? Or does that consume too much disk space?
bq. So. do you think if we can built and in tegrate the ARM CI running DEBUG,
RELEASE, LINT and IWYU testing job to Kudu community now ? we will also try to
find the root cause about TSAN and ASAN failures.
Let's address the IWYU issues and get DEBUG/RELEASE passing 100% of the time.
After that, we can do some basic integration by configuring the Zuul build to
e-mail d...@kudu.apache.org on failure.
> ARM/aarch64 platform support
> ----------------------------
>
> Key: KUDU-3007
> URL: https://issues.apache.org/jira/browse/KUDU-3007
> Project: Kudu
> Issue Type: Improvement
> Reporter: liusheng
> Priority: Critical
>
> As an import alternative of x86 architecture, Aarch64(ARM) architecture is
> currently the dominate architecture in small devices like phone, IOT devices,
> security cameras, drones etc. And also, there are more and more hadware or
> cloud vendor start to provide ARM resources, such as AWS, Huawei, Packet,
> Ampere. etc. Usually, the ARM servers are low cost and more cheap than x86
> servers, and now more and more ARM servers have comparative performance with
> x86 servers, and even more efficient in some areas.
> We want to propose to add an Aarch64 CI for KUDU to promote the support for
> KUDU on Aarch64 platforms. We are willing to provide machines to the current
> CI system and manpower to mananging the CI and fxing problems that occours.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
