I don't quite understand. You are saying tests don't pass yet, so why would anyone yet run these tests regularly? If it's because the instances aren't fast enough, use bigger instances? I don't think anyone would create a separate release of Spark for ARM, no. But why would that be necessary?
On Thu, Nov 14, 2019 at 7:28 PM bo zhaobo <bzhaojyathousa...@gmail.com> wrote: > Hi Spark team, > > Any ideas about the above email? Thank you. > > BR > > ZhaoBo > > > [image: Mailtrack] > <https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&;> > Sender > notified by > Mailtrack > <https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&;> > 19/11/15 > 上午09:26:17 > > Tianhua huang <huangtianhua...@gmail.com> 于2019年11月12日周二 下午2:47写道： > >> Hi all, >> >> Spark arm jobs have built for some time, and now there are two jobs[1] >> spark-master-test-maven-arm >> <https://amplab.cs.berkeley.edu/jenkins/job/spark-master-test-maven-arm/> >> and spark-master-test-python-arm >> <https://amplab.cs.berkeley.edu/jenkins/job/spark-master-test-python-arm/>, >> we can see there are some build failures, but it because of the poor >> performance of the arm instance, and now we begin to build spark arm jobs >> on other high performance instances, and the build/test are all success, we >> plan to donate the instance to amplab later. According to the build >> history, we are very happy to say spark is supported on aarch64 platform, >> and I suggest to add this good news into spark-3.0.0 releasenotes. Maybe >> community could provide an arm-supported release of spark at the meanwhile? >> >> [1] >> https://amplab.cs.berkeley.edu/jenkins/job/spark-master-test-maven-arm/ >> https://amplab.cs.berkeley.edu/jenkins/job/spark-master-test-python-arm/ >> >> ps: the jira https://issues.apache.org/jira/browse/SPARK-29106 trace the >> whole work, thank you very much Shane:) >> >
