[ 
https://issues.apache.org/jira/browse/KUDU-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17088242#comment-17088242
 ] 

liusheng commented on KUDU-3007:
--------------------------------

Hi [~adar]

Thanks for your suggestions, sorry for reply lately,  we have addressed the 
IWYU and LINT issues and adjust our CI mechines, for now, there are still 1~3 
tests failure sometimes when run CI job. but also all the test cases can pass 
sometimes. you can take a look following test results that show all the test 
cases passed:
http://80.158.17.129/logs/14/14/dd49799af27a7aaa6e8ad5e2c12913b69bc28991/check/kudu-build-test-aarch64-in-docker/f4e2161/test_results/release/console.log

For the randomly failed test cases we will continue to try to find root cause, 
but do you think if you can help to review and merge the patch: 
https://gerrit.cloudera.org/#/c/14964/ for now ? because we need to rebase 
patch again and again when debuging tests failures :)

Thanks a lot!

> 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)

Reply via email to