Hi @Sean Owen <sro...@gmail.com> , Thanks for your reply and patient. First, we are so apologized for the bad words in the previous emails. We just want to make the users can see the current support status in some place of spark community. I'm really appreciated that you and spark community make spark better on ARM, and open to us. Second, that's correct, adding this kind information of CICD into releasenotes is improper. So we won't do that. Third, I think your suggest is good for current situation. We will follow your kind suggestion and send a email to user@ and dev@ to describe our testing result, including the test coverage and the known issue we found. Also we hope that we do this could be good for attracting more users/developers of spark use ARM. Fourth, we still have concerns that user still can not know very clear that Spark can run on which ARCH with generic testing. So user will ask the same question again and again which mentioned by huangtianhua in spark community, eventhrough they plan to build/test on the specific ARCH. Here we are not true whether community has a good way to resolve this. Here just a suggest from us, how about describe the current testing status(all test status) of Amplab in some place of spark? Then users can know spark testing which already be pretested with generic test cases in upstream community, and feel confident to use spark on anyplace what they want according to that information.
In the end, we always believe community and follow community suggestions. Please feel free to tell us about our outcomes at work, and welcome to work together on Spark ARM. If any issue hit on ARM, please also @us for discuss. ;-) Thank you @Sean Owen <sro...@gmail.com> and team. 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/19 下午05:49:00 Sean Owen <sro...@apache.org> 于2019年11月18日周一 上午10:06写道： > Same response as before: > > - It is in the list of resolved JIRAs, of course > - It (largely) worked previously > - I think you're also saying you don't have 100% tests passing anyway, > though probably just small issues > - It does not seem to merit a special announcement from the PMC among > the 2000+ changes in Spark 3 > - You are welcome to announce (on the project's user@ list if you > like) whatever you want. Obviously, this is already well advertised on > dev@ > > I think you are asking for what borders on endorsement, and no that > doesn't sound appropriate. Please just announce whatever you like as > suggested. > > Sean > > On Sun, Nov 17, 2019 at 8:01 PM Tianhua huang <huangtianhua...@gmail.com> > wrote: > > > > @Sean Owen， > > I'm afraid I don't agree with you this time, I still remember no one can > tell me whether Spark supports ARM or how much Spark can support ARM when I > asked this first time on Dev@, you're very kind and told me to build and > test on ARM locally and so sorry I think you were not sure much about this > at that moment, right? Then I and my team work with community, we > found/fixed several issues, integrate arm jobs into AMPLAB Jenkins, and the > daily jobs has been stablely running for few weeks... after these efforts > why not announce this officially in Spark releasenote? I believe after this > everyone will know Spark is fully testing on ARM on community CI, Spark > supports ARM basically, it's amazing and this will be very helpful. So what > do you think? Or what are you worrying about? >
