Re: Jenkins PR build is failing

motely on qnode3 > <https://builds.apache.org/computer/qnode3> (ubuntu) in workspace > /home/jenkins/jenkins-slave/workspace/madlib-pr-build > > > -=e > > On Fri, Aug 18, 2017 at 10:53 AM, Nandish Jayaram <njaya...@pivotal.io> > wrote: > > > Hi, >

Jenkins PR build is failing

Hi, The latest PR build on Jenkins ( https://builds.apache.org/user/riyer/my-views/view/MADlib-Monitor/job/madlib-pr-build/170/) is failing with an `java.io.IOException: No space left on device` error. Can somebody with a Jenkins account have a look at it please? NJ

JIRA for migrating repos following MADlib's TLP graduation

Hi All, I have opened an Apache Infrastructure ticket to migrate MADlib's git repos, distribution server, and other common tasks associated with the move from incubator to TLP. The ticket is: https://issues.apache.org/jira/browse/INFRA-14872 Please do have a look at it and let me know if I have

Re: Jenkins madlib-master-build failed

Thank you for the info Ed. :) NJ On Fri, Aug 11, 2017 at 9:58 AM, Ed Espino wrote: > An observant badminton birdie whispered in the wind "I couldn't find a way > to re-trigger Jenkins master, is it because I don't have a Jenkins > account?" > > It just so happens that I

Re: [VOTE]: MADlib repo(s) migration

1 NJ On Wed, Aug 9, 2017 at 2:40 PM, Ed Espino <esp...@apache.org> wrote: > 2 > > Thanks NJ! > > On Wed, Aug 9, 2017 at 2:35 PM, Cooper Sloan <csl...@pivotal.io> wrote: > > > 2 > > > > On Wed, Aug 9, 2017 at 2:32 PM Nandish Jayaram &

[VOTE]: MADlib repo(s) migration

Hi All, With MADlib's graduation to TLP, it's time to migrate its github repos from `*incubator-madlib*` to `*madlib*`. We will have to open an Apache Infrastructure ticket to request this move for the following repos (along with other stuff like wiki, jenkins etc):

Re: Migrating MADlib code base out of incubator.

so support: "You are required to enable 2FA on GitHub > before you can gain write-access to repositories.". > > Shall we put the main MADlib repo(s) migration to GitBox to a vote? > > -=e > > On Wed, Aug 9, 2017 at 11:47 AM, Nandish Jayaram <njaya...@pivotal.io> > wro

Migrating MADlib code base out of incubator.

Hi All, I was planning on opening an Apache Infra JIRA to migrate MADlib's current code repo out of "incubator", following the directions in: https://incubator.apache.org/guides/transferring.html http://www.apache.org/dev/infra-contact#requesting-graduation An example Infra JIRA we can follow:

Confusion regarding the order of JIRAs to address

Hi All, I was reviewing PR #158 (https://github.com/apache/incubator-madlib/pull/158), and was also looking at the post graduation tasks. This PR seems to be very relevant to one of the post graduation JIRAs ( https://issues.apache.org/jira/browse/MADLIB-1132), and I was a little confused about

Re: MADlib Debugging (elastic_net) - MADLIB-1068

Nice catch, thanks Ed! NJ On Mon, Aug 7, 2017 at 2:07 PM, Ed Espino wrote: > I have resolved MADLIB-1068 with a workaround (use GCC 4 and not the > default GCC 5) for Ubuntu 16.04. I have created MADLIB-1145 to track the > GCC 5 issue. > > Happy Monday, > -=e > > On Fri, Aug

Re: Regarding moving source repos from incubator-madlib to madlib

> the Incubator" (https://incubator.apache.org/guides/transferring.html). > There is mention of the git project renaming task. > > There are also several TLP graduation JIRAs filed under the "TLP graduation > tasks" epic (https://issues.apache.org/jira/browse/MADLIB-1112). > &g

Regarding moving source repos from incubator-madlib to madlib

Hi All, Now that we have graduated to TLP, it's time to move all "incubator-madlib" to "madlib", and I was looking at a PR ( https://github.com/apache/incubator-madlib/pull/158) which does quite a bit towards it. I noticed that a few URLs such as our homepage and user docs (

Re: MADlib Python module code coverage

Hey Ed, I have not tried it. It'll be great if you could share your experiences with it. Will go well with https://github.com/apache/incubator-madlib/pull/151. NJ On Tue, Jul 18, 2017 at 3:34 PM, Ed Espino wrote: > MADlib dev, > > Has anyone tried to use the Python

Re: MADlib Code coverage

-directory gcov > > # You will notice there is some uninteresting system coverage info. > # The following will filter them out. > > lcov --remove coverage.info '/usr/include/*' '/usr/local/include/*' > '/usr/local/postgres/*' '*build/third_party/*' -o coverage_filtered.info >

Re: MADlib Code coverage

Hi Ed, We haven't set that up for MADlib yet, but we will be looking into it soon. Any ideas? NJ On Fri, Jul 14, 2017 at 10:00 AM, Ed Espino wrote: > Out of curiosity, do MADlib developers regularly use code coverage > utilities to measure the coverage quality of their

Re: [GitHub] incubator-madlib pull request #81: JIRA: MADLIB-927 Changes made in KNN-help...

Just pushing the code should be good, you don't have to create a new pull request. The existing one will get updated. NJ On Tue, Dec 27, 2016 at 5:56 PM, Kazmi,Auon H wrote: > Hi, > > I have been making some changes in existing KNN code after going through > the comments of

Re: [GitHub] incubator-madlib pull request #80: KNN Added

Hi Auon, You don't have to add the JIRA, it is already there: https://issues.apache.org/jira/browse/MADLIB-927 It's just good practice to mention the JIRA ID (JIRA: MADLIB-927) in your commit message. NJ On Sun, Dec 18, 2016 at 8:13 PM, Kazmi,Auon H wrote: > Hi NJ, > > I am

Re: [GitHub] incubator-madlib issue #80: KNN Added

struggled the most! NJ On Mon, Dec 19, 2016 at 9:51 AM, Nandish Jayaram <njaya...@pivotal.io> wrote: > Great! Let us know if you have any other questions. > > NJ > > On Fri, Dec 16, 2016 at 10:52 PM, Kazmi,Auon H <aka...@ufl.edu> wrote: > >> Hi NJ, >> >>

Re: [GitHub] incubator-madlib issue #80: KNN Added

dev@madlib.incubator.apache.org > Subject: Re: [GitHub] incubator-madlib issue #80: KNN Added > > Hi NJ, > > Thanks for your detailed reply! > > I will try to do the said things. > > > > Thanks, > > Auon > > __

Re: [GitHub] incubator-madlib issue #80: KNN Added

Hi Auon, Hope your exams went well. You can do whatever ends up being a better git-learning experience for you. Since you just started contributing to MADlib, the easier way to get going might be to do what you mentioned. But a better, though a longer way, would be to just mess around with

Re: Adding KNN to madlib

.apache.org > Subject: Re: Adding KNN to madlib > > Hi NJ, > > Thanks! > > I will do that. > > > > > Regards, > > Auon > > > From: Nandish Jayaram <njaya...@pivotal.io> > Sent: Sunday, December 4, 2016 1:39:53

Re: Adding KNN to madlib

; Subject: Re: Adding KNN to madlib > > Hi NJ, > > Thanks for your inputs! > > I will go through everyone of them and try to incorporate them. > > > > Regards, > > Auon Haidar > > > From: Nandish Jayaram <njaya...@pivo

Re: Adding KNN to madlib

nks for working on kNN for MADlib. Can you expand a little bit on your > note, and post the interface that you are thinking about and description of > the arguments? Then people can comment on that. > > Thanks, > Frank > > On Tue, Nov 15, 2016 at 9:30 AM, Nandish

Re: Adding KNN to madlib

Hi Auon, Great going with your first version of k-NN implementation. Some useful links for coding guidelines are at (see Developer Documentation): https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61319606 MADilb has something called as install-checks for basic testing. You can

Re: [VOTE] MADlib v1.9.1-rc2

+1 On Fri, Sep 2, 2016 at 10:26 AM, Frank McQuillan wrote: > Hello MADlib community, > > We have created a MADlib 1.9.1 RC-2, with the artifacts below up for a > vote. > > This release candidate replaces RC-1. The only difference between RC-1 and > RC-2 is > that some