Hi all,
I will give you some informations about ARM CI of Spark:
Our team and community are working on build/test Spark master on ARM64
server, after find and fix some issues[1], we have integrated two ARM
testing jobs[2] to community CI(AMPLAB Jenkins),
they run as daily job and have been
bviously, 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
ttps://mailtrack.io?utm_source=gmail_medium=signature_campaign=signaturevirality5;>
>> 19/11/15
>> 下午05:43:57
>>
>> Sean Owen 于2019年11月15日周五 下午5:04写道：
>>
>>> I don't think that's true either, not yet. Being JVM-based with no
>>> native code, I just don't
@Sean Owen,
Thanks for attention this.
I agree with you, it's probably not very appropriate to say 'support arm
from 3.0 release'. How about change to the word "Spark community supports
fully tests on arm from 3.0 release"?
Let's try to think about it from the user's point of view than
;>
>> BR
>>
>> ZhaoBo
>>
>>
>> [image: Mailtrack]
>> <https://mailtrack.io?utm_source=gmail_medium=signature_campaign=signaturevirality5;>
>> Sender
>> notified by
>> Mailtrack
>> <https://mailtrack.io?utm_source=gmail_med
he.org/jira/browse/SPARK-29106
>
>
>
> [image: Mailtrack]
> <https://mailtrack.io?utm_source=gmail_medium=signature_campaign=signaturevirality5;>
> Sender
> notified by
> Mailtrack
> <https://mailtrack.io?utm_source=gmail_medium=signature_campaign=signaturevirality5;
rt for the time being
> will be to create the job and 'best effort' for everything else.
>
> this should get us up and running asap.
>
> is there an open JIRA for jenkins/arm test support? we can move the
> technical details about this idea there.
>
> On Sun, Sep 15, 2019 at 9:03 PM Tianhu
uld continue with that for now.
>
> On Wed, Sep 11, 2019 at 10:06 PM Tianhua huang
> wrote:
>
>> Hi all,
>>
>> For the whole work process of spark ARM CI, we want to make 2 things
>> clear.
>>
>> The first thing is:
>> About spark ARM CI, now we have
rarely takes
> significant time, and there aren't project-specific mirrors here. You might
> be able to point at a closer public mirror, depending on where you are.
>
> On Thu, Aug 15, 2019 at 5:43 AM Tianhua huang
> wrote:
>
>> Hi all,
>>
>> I want to discuss spark
t's move forward. Waiting for your reply, thank you very
much.
On Wed, Aug 14, 2019 at 10:30 AM Tianhua huang
wrote:
> OK, thanks.
>
> On Tue, Aug 13, 2019 at 8:37 PM Sean Owen wrote:
>
>> -dev@ -- it's better not to send to the whole list to discuss specific
>> changes or
c..I found each of them seems run
>>>> the different CI job.
>>>>
>>>> @shane knapp,
>>>> Oh, sorry for disturb. I found your email looks like from 'berkeley.edu',
>>>> are you the good guy who we are looking for help about this? ;-)
>&g
@Sean Owen Thank you very much. And I saw your reply
comment in https://issues.apache.org/jira/browse/SPARK-28519, I will test
with modification and to see whether there are other similar tests fail,
and will address them together in one pull request.
On Sat, Jul 27, 2019 at 9:04 PM Sean Owen
(10, math.log(abs(a)))
res40: Double = 1.71669957511859558E18
I send an email to jdk-dev, hope someone can help, and also I proposed this
to JIRA https://issues.apache.org/jira/browse/SPARK-28519, , if you are
interesting, welcome to join and discuss, thank you very much.
On Thu, Jul 18, 2019 at 11
, Jul 17, 2019 at 8:37 PM Sean Owen wrote:
> On Wed, Jul 17, 2019 at 6:28 AM Tianhua huang
> wrote:
> > Two failed and the reason is 'Can't find 1 executors before 1
> milliseconds elapsed', see below, then we try increase timeout the tests
> passed, so wonder if we can in
failed tests fixing, we are waiting for your suggestions,
thank you very much.
On Wed, Jul 10, 2019 at 10:07 AM Tianhua huang
wrote:
> Hi all,
>
> I am glad to tell you there is a new progress of build/test spark on
> aarch64 server, the tests are running, see the build/test
/spark/pull/1
Now the tests are not all successful, I will try to fix it and any
suggestion is welcome, thank you all.
On Mon, Jul 1, 2019 at 5:25 PM Tianhua huang
wrote:
> We are focus on the arm instance of cloud, and now I use the arm instance
> of vexxhost cloud to run the build job
e NFS or one of google GCS, Azure WASB for the
>>> cluster FS. And before trying either of those cloud store, run the
>>> filesystem connector test suites (hadoop-azure; google gcs github) to see
>>> that they work. If the foundational FS test suites fail, nothing else
m and try to fix them, or at least report them. It's only
> worth getting CI in place when we think builds will work.
>
> On Tue, Jun 25, 2019 at 9:26 PM Tianhua huang
> wrote:
> >
> > Thanks Shane :)
> >
> > This sounds good, and yes I agree that it's best to keep
d in a arm-based docker container,
>> which (according to the intarwebs) is possible.
>>
>> shane
>>
>> On Tue, Jun 25, 2019 at 6:35 PM Tianhua huang
>> wrote:
>>
>>> I forked apache/spark project and propose a job(
>>> https://github.com/theopen
for spark. I also willing to be the maintainer of the arm ci
of spark.
Thanks for you attention.
On Thu, Jun 20, 2019 at 10:17 AM Tianhua huang
wrote:
> Thanks Sean.
>
> I am very happy to hear that the community will put effort to fix the
> ARM-related issues. I'd be happy to help
yeah, we don't have any aarch64 systems for testing... this has been
> asked before but is currently pretty low on our priority list as we don't
> have the hardware.
> >>>
> >>> sorry,
> >>>
> >>> shane
> >>>
> >>>
21 matches
Mail list logo
