It's mostly in this folder: https://github.com/apache/spark/tree/master/dev
Xin
On Wed, Feb 6, 2019 at 3:55 PM Tom Graves
wrote:
> I'm curious if we have it documented anywhere or if there is a good place
> to look, what exact commands Spark runs in the pull request builds and the
> QA builds?
seems like someone should investigate what caused the build time to go up
an hour and if it's expected or not.
On Thu, Jan 11, 2018 at 7:37 PM, Dongjoon Hyun
wrote:
> Hi, All and Shane.
>
> Can we increase the build time for `branch-2.3` during 2.3 RC period?
>
> There are two known test issues,
Most likely the job that uploads this stuff at databricks is broken.
On Thu, Dec 14, 2017 at 12:41 PM, Imran Rashid wrote:
> Hi,
>
> I was trying to look at some flaky tests and old jiras, and noticed that
> spark-tests.appspot.com is still live, but hasn't updated with any builds
> from the las
f
>> Holden Karau
>> *Sent:* Tuesday, November 7, 2017 2:14:18 PM
>> *To:* Sean Owen
>> *Cc:* Xin Lu; dev@spark.apache.org
>> *Subject:* Re: Jenkins upgrade/Test Parallelization & Containerization
>>
>> True, I think we've seen that the Amp Lab
nd when they come back, the PATH variable specified in the
>> workers' configs get dropped and we see behavior like this.
>>
>> josh rosen (whom i am talking with over chat) will be restarting the
>> ssh/worker processes on all of the worker nodes immediately. this will fix
>&g
nkins that was dedicated to it. Perhaps that's something that can be
replicated for OSS.
On Sun, Nov 5, 2017 at 8:45 AM, Xin Lu wrote:
> So, right now it looks like 2 and 6 are still broken, but 7 has recovered:
>
> https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA%20Test/job/
&
/.conda/envs/build/bin/python
>
> These steps look similar to how spark sets up its build. Not sure if this
> helps. Let me know if any other information would be helpful.
>
> Best,
>
> Alyssa Morrow
> akmor...@berkeley.edu
> 414-254-6645 <(414)%20254-6645>
&g
ssa (cc’ed) and I manage the mango build on the AMPLab Jenkins. I will
>> start to look into this to see what the connection between the mango builds
>> and the failing Spark builds are.
>>
>> Regards,
>>
>> Frank Austin Nothaft
>> fnoth...@berkeley.edu
&
cs.berkeley.edu
> 202-340-0466 <(202)%20340-0466>
>
> On Nov 4, 2017, at 9:15 PM, Xin Lu wrote:
>
> Sorry, mango wasn't added recently, but it looks like after successful
> builds of this specific configuration the workers break:
>
> https://amplab.cs.berkeley.ed
ns it recovers.
Xin
On Sat, Nov 4, 2017 at 9:09 PM, Xin Lu wrote:
> It has happened with other workers as well, namely 3 and 4 and then
> recovered. Looking at the build history it looks like a project called
> mango has been added to this pool of machines recently:
>
> https://am
It has happened with other workers as well, namely 3 and 4 and then
recovered. Looking at the build history it looks like a project called
mango has been added to this pool of machines recently:
https://amplab.cs.berkeley.edu/jenkins/job/mango/
It looks like the slaves start to fail spark pull re
Hi everyone,
I tried sending emails to this list and I'm not sure if it went through so
I'm trying again. Anyway, a couple months ago before I left Databricks I
was working on a proof of concept that parallelized Spark tests on
jenkins. The way it worked was basically it build the spark jars and
12 matches
Mail list logo
