Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214473135
i guess it just likes me more than you both. ;)
i'll triple-check the whitelist and see if something broke there. as
usual, there's nothing in the logs
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214470976
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214470548
it's because the github pull request builder generally sucks. :)
anyways, looking in to it now.
---
If your project is set up for it, you can reply
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-208622070
sounds good. i'm meeting w/the mesosphere guys thursday and this is a
topic i'm planning on bringing up.
On Mon, Apr 11, 2016 at 4:41 PM, Josh Rosen
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/11652#issuecomment-197601736
ok done
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/11652#issuecomment-197597252
i'm currently installing the latest lintr on all of our jenkins workers.
this should finish in ~15 mins
---
If your project is set up for it, you can reply
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/11652#issuecomment-196627128
hi!
i'll circle up w/shiv tomorrow and get this sorted. :)
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-185328477
the last failed build was due to a timeout reaching github... this is
something that's been ongoing now for a couple of years and it's definitely
on their end
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-185328415
jenkins test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/11051#issuecomment-183017267
the GHPRB plugin is finicky, obtuse and opaque in it's operations. i have
no idea why it decided to not trigger, and the logs don't show anything.
sorry
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-183021435
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-183034983
argh git timeout. jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/11100#issuecomment-182936788
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/11157#issuecomment-182936474
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/11136#issuecomment-182936359
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/10951#issuecomment-182936914
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/10949#issuecomment-182936276
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/8#issuecomment-182936245
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-182937916
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/10567#issuecomment-182936614
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/8#issuecomment-182945362
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/11051#issuecomment-182966961
jenkins test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/11051#issuecomment-182967337
im not totally sure... jenkins is picking up other PRB builds. i'll poke
around the (horrific) jenkins logs and see if i can't find out.
---
If your project
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/11051#issuecomment-182968845
it's building now:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51120/
---
If your project is set up for it, you can reply
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-180578099
so, it looks like our version of docker is old enough to fall in to
this category:
https://blog.docker.com/2015/10/docker-hub-deprecation-1-5
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/10300#issuecomment-164597672
lgtm
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/9765#issuecomment-164541241
jenkins test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/10276#issuecomment-164541277
jenkins test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/10238#issuecomment-164541189
jenkins test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/10238#issuecomment-164532828
jenkins test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/9765#issuecomment-164532981
jenkins test this plese
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/10276#issuecomment-164532877
jenkins test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/9736#issuecomment-157165188
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/9736#issuecomment-157164906
i'm gonna kill this job -- it's hanging on amp-jenkins-worker-07 and eating
up machine resources. i'll kick it back off after i clean up.
---
If your project
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/8923#issuecomment-156474692
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/8923#issuecomment-156446782
i will retrigger the build after jenkins maintenance is done.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user shaneknapp closed the pull request at:
https://github.com/apache/spark/pull/9547
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
GitHub user shaneknapp opened a pull request:
https://github.com/apache/spark/pull/9547
whitespace change, do not merge
testing the amplab jenkins bot
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shaneknapp/spark
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/9528#issuecomment-154532392
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/8643#issuecomment-154543591
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/8908#issuecomment-144189560
huh, i haven't seen that error message either. when i run that command
locally (same box, same working dir, jenkins user), it works. i'll try and
keep an eye out
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/8908#issuecomment-144277996
i'll take a closer look tomorrow, @shivaram.
On Tue, Sep 29, 2015 at 8:41 PM, Shivaram Venkataraman <
notificati...@github.com>
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143935192
i'll take a look at the config tomorrow
On Mon, Sep 28, 2015 at 6:02 PM, gliptak <notificati...@github.com> wrote:
>
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/8905#issuecomment-142957941
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/8903#issuecomment-142957758
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143069705
could you create a spark issue for the plugin and assign it to me?
also, i won't be able to do this until monday, as i'm about to leave town
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/8793#issuecomment-141105891
LGTM! make it so!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/8239#issuecomment-132769344
Whoops, bad bash on my part. I'll be in shortly and will fix that right
up.
On Aug 19, 2015 11:36 AM, Apache Spark QA notificati...@github.com
wrote
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/7883#issuecomment-132343883
found one directory on amp-jenkins-worker-01 that's polluted -- deleting it
now, and this should fix any builds that run there.
On Mon, Aug 17, 2015 at 9
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/7883#issuecomment-132070168
On Mon, Aug 17, 2015 at 10:11 AM, Shivaram Venkataraman
notificati...@github.com wrote:
@JoshRosen https://github.com/JoshRosen There seems to be some
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/7883#issuecomment-127653248
alright, lintr is installed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/7883#issuecomment-127431878
yep, i'm on it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/7883#issuecomment-127404207
i'm installing lintr now on all the workers
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/7883#issuecomment-127406094
@yu-iskw -- i did indeed use the cran version:
Rscript -e 'install.packages(lintr, repos=http://cran.stat.ucla.edu/;)'
got a link to the more recent
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/7883#issuecomment-127399644
i'm actually here until tomorrow, so i can get this installed pretty
easily...
On Mon, Aug 3, 2015 at 1:06 PM, Josh Rosen notificati...@github.com wrote
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/7554#issuecomment-126087467
sorry, my fault. i broke the build, and have reverted my change to
jenkins. :)
jenkins, test this please
---
If your project is set up for it, you can
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/7739#issuecomment-126087799
sorry, i broke the jenkins config and have since reverted my change. allow
me to retrigger your build... :)
jenkins, test this please
---
If your project
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/7432#issuecomment-126088001
sorry, i broke the jenkins config and have since reverted my change. allow
me to retrigger your build... :)
jenkins, test this please
---
If your project
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/7564#issuecomment-125738959
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/7401#issuecomment-125310764
I'm ooo today and can check tomorrow
On Jul 27, 2015 10:57 AM, Brennon York notificati...@github.com wrote:
@shaneknapp https://github.com/shaneknapp do
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/7584#issuecomment-123780351
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/7584#issuecomment-123780334
yeah, the jar file is truly corrupted. let's retrigger the build and see
what happens, and i'll poke around and see if i can't get to the bottom of what
happened
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/7584#issuecomment-123795911
i was *hoping* that the build would run on a different worker, but alas...
-06 it was!
anyways, i just checked the jar on all of the workers and they're
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/7369#issuecomment-120947321
i'll retrigger this build once the jenkins system updates are completed
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/7369#issuecomment-120999513
jenkins test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/7369#issuecomment-120996539
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/7139#issuecomment-118926294
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/7139#issuecomment-118193954
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/7139#issuecomment-117848496
@shivaram -- i'm looking in to the bash monstrosities and seeing if it's
somehow missing an exit code... to this end i'm setting up some test builds on
our staging
Github user shaneknapp commented on a diff in the pull request:
https://github.com/apache/spark/pull/5694#discussion_r32121121
--- Diff: dev/run-tests.py ---
@@ -0,0 +1,508 @@
+#!/usr/bin/env python2
+
+#
+# Licensed to the Apache Software Foundation (ASF) under one
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5694#issuecomment-110823701
btw, we are currently setting the PATH variable for python3/anaconda in the
both this script as well as in the build config on jenkins. this makes for a
sad shane
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5694#issuecomment-110813146
@brennonyork -- yep, you're right. :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/6623#issuecomment-108627303
thanks shiv, you beat me to it. lgtm.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/6454#issuecomment-106328291
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/6454#issuecomment-106347876
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp closed the pull request at:
https://github.com/apache/spark/pull/5817
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5817#issuecomment-106080678
closing this PR, as @brennonyork 's work on
https://github.com/apache/spark/pull/5694 will address some of this.
---
If your project is set up for it, you can reply
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5694#issuecomment-105258702
outside of the merge conflicts, lgtm!
On Thu, May 21, 2015 at 2:08 PM, Brennon York notificati...@github.com
wrote:
Thanks @davies https
Github user shaneknapp commented on a diff in the pull request:
https://github.com/apache/spark/pull/5694#discussion_r30631345
--- Diff: dev/run-tests.py ---
@@ -0,0 +1,418 @@
+#!/usr/bin/env python
+
+#
+# Licensed to the Apache Software Foundation (ASF) under one
Github user shaneknapp commented on a diff in the pull request:
https://github.com/apache/spark/pull/5694#discussion_r30617537
--- Diff: dev/run-tests.py ---
@@ -0,0 +1,418 @@
+#!/usr/bin/env python
+
+#
+# Licensed to the Apache Software Foundation (ASF) under one
Github user shaneknapp commented on a diff in the pull request:
https://github.com/apache/spark/pull/5694#discussion_r30634573
--- Diff: dev/run-tests.py ---
@@ -0,0 +1,418 @@
+#!/usr/bin/env python
+
+#
+# Licensed to the Apache Software Foundation (ASF) under one
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5786#issuecomment-102132344
@srowen -- so i'm looking at the configs and we don't actually specify
anything in the builds WRT to mvn or sbt build options[1]. these are all
matrix build configs
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/6085#issuecomment-101666364
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/6085#issuecomment-101665695
i will retrigger this job once i restart jenkins
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5694#issuecomment-101739530
@nchammas -- the tests run against 2.6.6, 2.7.9 (pypy 2.5.1) and 3.4.3.
for this script 2.6 or 2.7 will be fine, and will actually execute with 2.7.9
in our test
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5694#issuecomment-101456318
yes absolutely, i will put some eyes on this!
a quick question: is there a specific version of python we want to run
this under? currently
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5871#issuecomment-100249806
i'll retrigger this job once i restart jenkins
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5423#issuecomment-100253786
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5959#issuecomment-100253882
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5959#issuecomment-100249349
i'll retrigger this job once i restart jenkins
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5423#issuecomment-100248827
i'll retrigger this job once i restart jenkins.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5871#issuecomment-100253953
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp closed the pull request at:
https://github.com/apache/spark/pull/5910
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5877#issuecomment-99894586
i'll retrigger this build once jenkins is back up...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5877#issuecomment-99900643
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5980#issuecomment-99894548
i'll retrigger this build once jenkins is back up...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5980#issuecomment-99900602
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5938#issuecomment-99601561
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5910#issuecomment-99541194
jenkins, build this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5938#issuecomment-99550932
@shivaram -- you're an admin. looks like what patrick is saying is the
cause.
jenkins, test this please
---
If your project is set up for it, you can reply
401 - 500 of 654 matches
Mail list logo
