Great work Tianhua! This is a very exciting enhancement.
dev@ isn't usually meant for automated test run output. Would it be possible to get the openlabtesting runs triggered by jenkins.impala.io then have the results of the test run come from that jenkins instance? This should solve the email problem as the notification can come from the jenkins account and still give us one centralized place to look at various test statuses. -Shant On Thu, Sep 17, 2020 at 8:08 AM Tianhua huang <huangtianhua...@gmail.com> wrote: > Hi all, > > Impala can run/test on arm64 platform after our efforts, the issues we > fixed you can find in https://issues.apache.org/jira/browse/IMPALA-9376 > > We are particularly grateful to Tim and Quanlong for their help, thanks > very much! > > And I have integrated Impala arm64 CI with OpenLab( > https://openlabtesting.org/ , a community to do open source project > testing), > see > http://status.openlabtesting.org/builds?job_name=impala-build-test-arm64 > the > periodic test job runs for a few days already and runs once per day. > > Tim suggested us to send the arm64 test result to > comm...@impala.apache.org, > but seems it can receive the emails only ncome from @apache.org. > Now I wonder if we can send the test result to Impala community maillist > here dev@impala.apache.org, to tell developers that Impala can runs on > arm64, to find the compatibility in time. > > What do you think? Or maybe there is any other good suggestion? > > Waiting for your reply. > > Thank you very much! >
