Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5910#issuecomment-99543031
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-99659725
@shivaram -- i seriously have no clue as to what's going on... you're an
overall GHPRB admin for amplab jenkins, as well as for the spark PRB (as am i).
anyways
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5938#issuecomment-99657929
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-99657911
sigh.
---
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/5938#issuecomment-99657960
(i think we're due a jenkins restart tomorrow morning)
---
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/5938#issuecomment-99660165
@shivaram -- can you try and trigger another build? i've increased the log
chattiness and hopefully i can see what's happening now.
---
If your project is set up
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5446#issuecomment-99248943
yep. i'll take worker 03 offline until i can get a chance to investigate
(i'm OOO this afternoon).
Thanks for the catch!
@shaneknapp https
GitHub user shaneknapp opened a pull request:
https://github.com/apache/spark/pull/5910
WHITESPACE CHANGE DO NOT MERGE
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shaneknapp/spark whitespace_change
Alternatively you can
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5786#issuecomment-98434090
ah cool, got it. thanks sean!
On Sat, May 2, 2015 at 3:49 AM, Sean Owen notificati...@github.com wrote:
@shaneknapp https://github.com/shaneknapp
Github user shaneknapp commented on a diff in the pull request:
https://github.com/apache/spark/pull/5817#discussion_r29508843
--- Diff: dev/run-tests-jenkins ---
@@ -171,15 +171,14 @@ for t in ${PR_TESTS[@]}; do
# Ensure the test can be found and is a file
if [ -f
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5817#issuecomment-98161829
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/5817#issuecomment-98179614
jenkins, test this please
On Fri, May 1, 2015 at 9:57 AM, UCB AMPLab notificati...@github.com wrote:
Test FAILed.
Refer to this link for build
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5786#issuecomment-98219552
what exactly will need to be changed in the build configs? there's a lot
of places that hadoop is specified: multi-project axis configs, maven opts
(for other
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5817#issuecomment-98203869
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 not have
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5817#issuecomment-98237474
alright, this looks to be all i can winnow out of the maze of build scripts
right now... i'll open up another PR if i find more offending stuff. :)
---
If your
Github user shaneknapp commented on a diff in the pull request:
https://github.com/apache/spark/pull/5817#discussion_r29533973
--- Diff: dev/run-tests-jenkins ---
@@ -171,15 +171,14 @@ for t in ${PR_TESTS[@]}; do
# Ensure the test can be found and is a file
if [ -f
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5817#issuecomment-98240563
@pwendell -- no worries, this is mostly to just clean up noisy build logs.
we can revisit this whenever you're ready.
---
If your project is set up for it, you can
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5694#issuecomment-98242052
@nchammas -- totally understood! :)
@brennonyork -- i'm looking forward to spending some time digging in to
this code next week
---
If your project is set
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5784#issuecomment-97909684
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/5784#issuecomment-97894913
so, believe it or not, the jenkins bash environment is actually atomic (all
machines are identical hardware, same kernel, system updates, package versions,
ssh bash
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5817#issuecomment-97927713
@brennonyork
---
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 opened a pull request:
https://github.com/apache/spark/pull/5817
redir stderr better, remove unused code, better java exe detection
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/5817#issuecomment-97970305
ok, happened to me, too! investigating...
---
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/5817#issuecomment-97927914
i see a couple more spots i could /dev/null stuff... looking again, and
another commit or two forthcoming
---
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/5817#issuecomment-98008939
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 not have
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5784#issuecomment-97610281
@brennonyork -- something seems strange w/the output of
pr_public_classes.sh...
i checked the jenkins output also, and it's reporting that the SHA1 is
SHA1
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5173#issuecomment-97603182
ignore these comments -- this is me testing on our staging instance
---
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/5667#issuecomment-96755037
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 not have
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5667#issuecomment-96751693
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 not have
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5667#issuecomment-96766146
ok, fixed
On Sat, Apr 25, 2015 at 1:36 PM, shane knapp â incompl...@gmail.com
wrote:
I'm out of town for the weekend. I can check Sunday night
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5667#issuecomment-96275266
I'm out of town for the weekend. I can check Sunday night.
On Apr 25, 2015 12:17 PM, Shivaram Venkataraman notificati...@github.com
wrote:
@shaneknapp
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5615#issuecomment-94912457
guess i forgot to log myself out of the amplab account. :)
lgtm!
---
If your project is set up for it, you can reply to this email and have your
reply
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5173#issuecomment-93862558
woot!
On Thu, Apr 16, 2015 at 4:22 PM, Josh Rosen notificati...@github.com
wrote:
I've merged this into master (1.4.0). Thanks @davies
https
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5173#issuecomment-91679811
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/5432#issuecomment-91358326
so i just grepped through the code and found stuff like this:
yarn/src/main/scala/org/apache/spark/deploy/yarn/Client.scala
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5424#issuecomment-91322259
whoops, i missed retriggering this build. :)
jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5432#issuecomment-91358660
btw i prefer #2.
---
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/5424#issuecomment-91274650
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/5400#issuecomment-91274692
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/5432#issuecomment-91360942
oh, i just had a thought: i installed a couple of different versions of
java through jenkins, and right now the tests are set in the config to use
'Default', which
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5432#issuecomment-91360301
cool. on our systems, at least, the system java we use is /usr/bin/java,
which points (through /etc/alternatives), to /usr/java/latest (which itself is
a link
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5213#issuecomment-91274674
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/5096#issuecomment-91041894
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/5096#issuecomment-91040738
i'll up it to 180, just so we have some headroom.
On Wed, Apr 8, 2015 at 2:21 PM, Shivaram Venkataraman
notificati...@github.com wrote
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5096#issuecomment-91041984
also, i can't believe how long this build is... sad panda etc.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5277#issuecomment-87874009
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/5277#issuecomment-87873998
whoops, my bad. didn't mean to kill this job.
---
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/5248#issuecomment-87874066
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/5248#issuecomment-87874061
whoops, my bad. didn't mean to kill this job. retesting now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5046#issuecomment-81802097
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/5036#issuecomment-81804505
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/5042#issuecomment-81790432
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/5046#issuecomment-81736014
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/5046#issuecomment-81752785
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/5046#issuecomment-81729919
this was me, i'll retrigger the job once maintenance is over.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5046#issuecomment-81745711
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/4733#issuecomment-79283689
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/3699#issuecomment-79274011
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/4964#issuecomment-79375896
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/3699#issuecomment-79376311
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/4986#issuecomment-79307244
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/4964#issuecomment-79291957
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/4986#issuecomment-79375733
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/4733#issuecomment-79376104
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/5018#issuecomment-79376490
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/4913#issuecomment-77396021
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/4774#issuecomment-77410205
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/4901#issuecomment-77409790
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/4913#issuecomment-77390948
i will retrigger this test once we're done w/our maintenance.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/4677#issuecomment-74958110
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/4677#issuecomment-74958129
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/3798#issuecomment-71975308
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/4260#issuecomment-71975248
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/4259#issuecomment-71975286
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/4264#issuecomment-71975278
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/4260#issuecomment-71975259
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/4263#issuecomment-71975294
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/4263#issuecomment-71975044
i will kick this off again 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/4259#issuecomment-71975031
i will kick this off again 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/4260#issuecomment-71975104
i will kick this off again 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/4264#issuecomment-71975011
i will kick this off again 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/3798#issuecomment-71975061
i will kick this off again 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/2914#issuecomment-67101629
jenkins, test this
---
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/2854#issuecomment-66796958
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/2854#issuecomment-66797630
testing the numpy version bump now
---
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
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/2854#issuecomment-66804428
ok, i think we're good on the numpy front -- it's failing now in new and
exciting ways. :)
---
If your project is set up for it, you can reply to this email
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/3668#issuecomment-66835922
woot! :)
On Fri, Dec 12, 2014 at 12:47 PM, UCB AMPLab notificati...@github.com
wrote:
Test PASSed.
Refer to this link for build results
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/3564#issuecomment-66837976
i'm gonna kill the 22418 build and retrigger. need to restart jenkins
really quick.
---
If your project is set up for it, you can reply to this email and have your
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/3564#issuecomment-66838097
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/3564#issuecomment-66838179
thanks for the patience @nchammas ! :)
---
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/3668#issuecomment-66677019
would you guys be adverse to me upping the numpy version on the workers?
currently, we're running numpy-1.4.1-9.el6.x86_64, which is ancient compared
to the LG
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/2854#issuecomment-66677820
https://github.com/apache/spark/pull/3668
looks like a numpy upgrade is coming.
---
If your project is set up for it, you can reply to this email and have
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/3668#issuecomment-66702325
ok, sgtm. since we're not blocking the release, i'll just get everything
staged and do the upgrade during the scheduled maintenance tomorrow morning.
---
If your
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/2854#issuecomment-66702369
we'll do the numpy upgrade tomorrow morning during the scheduled outage.
---
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/2854#issuecomment-66375546
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/2914#issuecomment-66375507
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/2854#issuecomment-66377357
i'm going to fail this job as i need to restart the jenkins worker that
this is on. after that i will retrigger the build. sorry for the
inconvenience
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/2854#issuecomment-66379552
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/2854#issuecomment-66392666
all of our worker nodes have numpy-1.4.1-9.el6.x86_64 installed on them,
and have had this for months. i'm home for the evening, but we can do git
archaeology
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/3381#issuecomment-64316830
i'll have the time to take a closer look at this tomorrow.
On Mon, Nov 24, 2014 at 9:59 PM, Daoyuan Wang notificati...@github.com
wrote
501 - 600 of 654 matches
Mail list logo
