[jira] [Updated] (MADLIB-1145) Ubuntu 16.04 - Using GCC 5 (default gcc) causes Postgres 9.6 crash

[Ed Espino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MADLIB-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino updated MADLIB-1145:
--
Fix Version/s: v2.0

> Ubuntu 16.04 - Using GCC 5 (default gcc) causes Postgres 9.6 crash
> --
>
> Key: MADLIB-1145
> URL: https://issues.apache.org/jira/browse/MADLIB-1145
> Project: Apache MADlib
>  Issue Type: Bug
>  Components: Build System
>Reporter: Ed Espino
> Fix For: v2.0
>
>
> Upon analysis of MADLIB-1068, it was determined that the GCC 5 compiler which 
> is available on Ubuntu 16.04 causes MADlib to produce a Postgres 9.6 crash. 
> This JIRA will capture the GCC 5 issues.
> Please refer to Ubuntu 16.04 MADLIB-1068 for crash details and the workaround 
> (use GCC 4).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (MADLIB-1118) Reduce size of elastic net install check table

[Ed Espino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MADLIB-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino resolved MADLIB-1118.
---
Resolution: Fixed

Merged to master.

> Reduce size of elastic net install check table
> --
>
> Key: MADLIB-1118
> URL: https://issues.apache.org/jira/browse/MADLIB-1118
> Project: Apache MADlib
>  Issue Type: Task
>  Components: Module: Regularized Regression
>Reporter: Frank McQuillan
>Assignee: Ed Espino
>Priority: Minor
> Fix For: v1.12
>
>
> IC is taking too long for elastic net.  I would suggest we reduce the size of 
> the input data table.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (MADLIB-1133) TLP graduation - remove references to "incubating" in source tree

[Ed Espino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MADLIB-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino resolved MADLIB-1133.
---
Resolution: Fixed

This has been merged to master branch.

> TLP graduation  - remove references to "incubating" in source tree
> --
>
> Key: MADLIB-1133
> URL: https://issues.apache.org/jira/browse/MADLIB-1133
> Project: Apache MADlib
>  Issue Type: Task
>  Components: All Modules
>Reporter: Frank McQuillan
>Assignee: Ed Espino
>Priority: Minor
> Fix For: v1.12
>
>
>  Source tree incubation references. Run
>"ack -i incubat" 
> command on the master branch and make appropriate updates as per the output



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (MADLIB-1005) Cannot compile for greenplum (arch linux) - AggCheckCallContext issue

[Ed Espino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MADLIB-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino resolved MADLIB-1005.
---
Resolution: Fixed

This was fixed back in January 2017 with the following commit:

{code}
git show -s 3cf3f6771ab51dd26605ce4d70cd70aee5d896dd
commit 3cf3f6771ab51dd26605ce4d70cd70aee5d896dd
Author: Dave Cramer 
Date:   Wed Jan 11 15:17:01 2017 -0800

Build: Exclude AggCheckCallContext for GPDB5

- Adds build files to compile MADlib with GPDB5
- GPDB5 cherrypicked AggCheckCallContext, we have to exclude it for GPDB5 
builds

Closes #83
{code}

I have verified this with GPDB 5 (7789b1a5fd18338b454396d5281a6127c9a9ee8a - 
{{configure --disable-orca --with-python}}) and MADlib 
(4e8616b7a9c0a21326b906ff534d341fab8a5fa4) on CentOS Linux release 7.3.1611 
(Core).

{code}
$ /usr/local/madlib/bin/madpack -s madlib -p greenplum install-check

madpack.py : INFO : Detected Greenplum DB version 5.0.0.
TEST CASE RESULT|Module: array_ops|array_ops.sql_in|PASS|Time: 582 milliseconds
TEST CASE RESULT|Module: bayes|gaussian_naive_bayes.sql_in|PASS|Time: 806 
milliseconds
TEST CASE RESULT|Module: bayes|bayes.sql_in|PASS|Time: 2032 milliseconds
TEST CASE RESULT|Module: crf|crf_train_small.sql_in|PASS|Time: 980 milliseconds
TEST CASE RESULT|Module: crf|crf_train_large.sql_in|PASS|Time: 1389 milliseconds
TEST CASE RESULT|Module: crf|crf_test_small.sql_in|PASS|Time: 852 milliseconds
TEST CASE RESULT|Module: crf|crf_test_large.sql_in|PASS|Time: 1019 milliseconds
TEST CASE RESULT|Module: 
elastic_net|elastic_net_install_check.sql_in|PASS|Time: 79703 milliseconds
TEST CASE RESULT|Module: linalg|svd.sql_in|PASS|Time: 7446 milliseconds
TEST CASE RESULT|Module: linalg|matrix_ops.sql_in|PASS|Time: 6264 milliseconds
TEST CASE RESULT|Module: linalg|linalg.sql_in|PASS|Time: 341 milliseconds
TEST CASE RESULT|Module: prob|prob.sql_in|PASS|Time: 1213 milliseconds
TEST CASE RESULT|Module: sketch|support.sql_in|PASS|Time: 49 milliseconds
TEST CASE RESULT|Module: sketch|mfv.sql_in|PASS|Time: 263 milliseconds
TEST CASE RESULT|Module: sketch|fm.sql_in|PASS|Time: 1782 milliseconds
TEST CASE RESULT|Module: sketch|cm.sql_in|PASS|Time: 6164 milliseconds
TEST CASE RESULT|Module: svm|svm.sql_in|PASS|Time: 13794 milliseconds
TEST CASE RESULT|Module: tsa|arima_train.sql_in|PASS|Time: 3856 milliseconds
TEST CASE RESULT|Module: tsa|arima.sql_in|PASS|Time: 3622 milliseconds
TEST CASE RESULT|Module: conjugate_gradient|conj_grad.sql_in|PASS|Time: 347 
milliseconds
TEST CASE RESULT|Module: knn|knn.sql_in|PASS|Time: 483 milliseconds
TEST CASE RESULT|Module: lda|lda.sql_in|PASS|Time: 3117 milliseconds
TEST CASE RESULT|Module: stats|wsr_test.sql_in|PASS|Time: 171 milliseconds
TEST CASE RESULT|Module: stats|t_test.sql_in|PASS|Time: 259 milliseconds
TEST CASE RESULT|Module: 
stats|robust_and_clustered_variance_coxph.sql_in|PASS|Time: 1125 milliseconds
TEST CASE RESULT|Module: stats|pred_metrics.sql_in|PASS|Time: 1015 milliseconds
TEST CASE RESULT|Module: stats|mw_test.sql_in|PASS|Time: 126 milliseconds
TEST CASE RESULT|Module: stats|ks_test.sql_in|PASS|Time: 336 milliseconds
TEST CASE RESULT|Module: stats|f_test.sql_in|PASS|Time: 127 milliseconds
TEST CASE RESULT|Module: stats|cox_prop_hazards.sql_in|PASS|Time: 2430 
milliseconds
TEST CASE RESULT|Module: stats|correlation.sql_in|PASS|Time: 1107 milliseconds
TEST CASE RESULT|Module: stats|chi2_test.sql_in|PASS|Time: 378 milliseconds
TEST CASE RESULT|Module: stats|anova_test.sql_in|PASS|Time: 267 milliseconds
TEST CASE RESULT|Module: svec_util|svec_test.sql_in|PASS|Time: 1567 milliseconds
TEST CASE RESULT|Module: svec_util|gp_sfv_sort_order.sql_in|PASS|Time: 126 
milliseconds
TEST CASE RESULT|Module: utilities|text_utilities.sql_in|PASS|Time: 288 
milliseconds
TEST CASE RESULT|Module: utilities|sessionize.sql_in|PASS|Time: 421 milliseconds
TEST CASE RESULT|Module: utilities|pivot.sql_in|PASS|Time: 1398 milliseconds
TEST CASE RESULT|Module: utilities|path.sql_in|PASS|Time: 439 milliseconds
TEST CASE RESULT|Module: utilities|encode_categorical.sql_in|PASS|Time: 735 
milliseconds
TEST CASE RESULT|Module: utilities|drop_madlib_temp.sql_in|PASS|Time: 165 
milliseconds
TEST CASE RESULT|Module: assoc_rules|assoc_rules.sql_in|PASS|Time: 1833 
milliseconds
TEST CASE RESULT|Module: convex|mlp.sql_in|PASS|Time: 14029 milliseconds
TEST CASE RESULT|Module: convex|lmf.sql_in|PASS|Time: 3226 milliseconds
TEST CASE RESULT|Module: glm|poisson.sql_in|PASS|Time: 1309 milliseconds
TEST CASE RESULT|Module: glm|ordinal.sql_in|PASS|Time: 1002 milliseconds
TEST CASE RESULT|Module: glm|multinom.sql_in|PASS|Time: 1184 milliseconds
TEST CASE RESULT|Module: glm|inverse_gaussian.sql_in|PASS|Time: 1604 
milliseconds
TEST CASE RESULT|Module: glm|gaussian.sql_in|PASS|Time: 1349 milliseconds
TEST CASE RESULT|Module: glm|gamma.sql_in|PASS|Time: 6276 milliseconds
TEST CASE RESULT|Module: glm|binomial.sql_in|PASS|Time: 

[jira] [Commented] (MADLIB-1103) Remove pyxb GPL workaround

[Ed Espino (JIRA)]

[ 
https://issues.apache.org/jira/browse/MADLIB-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16119507#comment-16119507
 ] 

Ed Espino commented on MADLIB-1103:
---

The fix will be made available in the PyXB 1.2.6 release. It is not clear when 
it will be made available. I suggest we push this to the next release.

> Remove pyxb GPL workaround
> --
>
> Key: MADLIB-1103
> URL: https://issues.apache.org/jira/browse/MADLIB-1103
> Project: Apache MADlib
>  Issue Type: Improvement
>  Components: Build System
>Reporter: Roman Shaposhnik
>Priority: Minor
> Fix For: v1.12
>
>
> Upstream pyxb has done the right thing and got rid of GPL code: 
> https://github.com/pabigot/pyxb/issues/77
> It would be great to remove workaround from MADlib



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (MADLIB-1118) Reduce size of elastic net install check table

[Ed Espino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MADLIB-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino reassigned MADLIB-1118:
-

Assignee: Ed Espino

> Reduce size of elastic net install check table
> --
>
> Key: MADLIB-1118
> URL: https://issues.apache.org/jira/browse/MADLIB-1118
> Project: Apache MADlib
>  Issue Type: Task
>  Components: Module: Regularized Regression
>Reporter: Frank McQuillan
>Assignee: Ed Espino
>Priority: Minor
> Fix For: v1.12
>
>
> IC is taking too long for elastic net.  I would suggest we reduce the size of 
> the input data table.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MADLIB-1145) Ubuntu 16.04 - Using GCC 5 (default gcc) causes Postgres 9.6 crash

[Ed Espino (JIRA)]

[ 
https://issues.apache.org/jira/browse/MADLIB-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16117817#comment-16117817
 ] 

Ed Espino commented on MADLIB-1145:
---

[~okislal] - I added a new one as this one does not impact compilation. The 
compilation is fine with GCC 5. Unfortunately, it causes Postgres to crash on 
the execution of several MADlib install-checks.

For reference: MADLIB-1025 - MADlib does not compile with gcc 6.2

> Ubuntu 16.04 - Using GCC 5 (default gcc) causes Postgres 9.6 crash
> --
>
> Key: MADLIB-1145
> URL: https://issues.apache.org/jira/browse/MADLIB-1145
> Project: Apache MADlib
>  Issue Type: Bug
>  Components: Build System
>Reporter: Ed Espino
>
> Upon analysis of MADLIB-1068, it was determined that the GCC 5 compiler which 
> is available on Ubuntu 16.04 causes MADlib to produce a Postgres 9.6 crash. 
> This JIRA will capture the GCC 5 issues.
> Please refer to Ubuntu 16.04 MADLIB-1068 for crash details and the workaround 
> (use GCC 4).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MADLIB-1112) TLP graduation tasks

[Ed Espino (JIRA)]

[ 
https://issues.apache.org/jira/browse/MADLIB-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16117394#comment-16117394
 ] 

Ed Espino commented on MADLIB-1112:
---

For reference, one of the excelent project mentors (namely: [~rvs]) pointed me 
at the following: [Guide :: Transferring Resources out of the 
Incubator|https://incubator.apache.org/guides/transferring.html].

> TLP graduation tasks
> 
>
> Key: MADLIB-1112
> URL: https://issues.apache.org/jira/browse/MADLIB-1112
> Project: Apache MADlib
>  Issue Type: Epic
>  Components: All Modules
>Reporter: Frank McQuillan
>Assignee: Frank McQuillan
> Fix For: v1.12
>
>
> This is the epic for the set of TLP graduation tasks



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (MADLIB-1144) Remove DISCLAIMER file once MADlib registered trademark has been fully transferred to ASF.

[Ed Espino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MADLIB-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino reassigned MADLIB-1144:
-

Assignee: (was: Ed Espino)

> Remove DISCLAIMER file once MADlib registered trademark has been fully 
> transferred to ASF.
> --
>
> Key: MADLIB-1144
> URL: https://issues.apache.org/jira/browse/MADLIB-1144
> Project: Apache MADlib
>  Issue Type: Task
>Reporter: Ed Espino
>
> Post TLP graduation activities, we will be retaining the DISCLAIMER file 
> referencing the MADlib trademark transition activity noted in 
> PODLINGNAMESEARCH-125. This task will be used to track the removal of the 
> DISCLAIMER file once the trademark is fully transferred to ASF.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (MADLIB-1068) madpack install-check fails on PostgreSQL 9.6.2 & Ubuntu 16.04.2

[Ed Espino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MADLIB-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino resolved MADLIB-1068.
---
Resolution: Workaround

Use GCC 4 to build MADlib. The following information on the project's wiki has 
been updated with this information.

https://cwiki.apache.org/confluence/display/MADLIB/Installation+Guide#InstallationGuide-CompileFromSourceCompilingFromSource

MADLIB-1145 has been created to track the GCC 5 issue.

> madpack install-check fails on PostgreSQL 9.6.2 & Ubuntu 16.04.2
> 
>
> Key: MADLIB-1068
> URL: https://issues.apache.org/jira/browse/MADLIB-1068
> Project: Apache MADlib
>  Issue Type: Question
>  Components: Madpack
>Reporter: John Grant
>Assignee: Ed Espino
> Fix For: v1.12
>
> Attachments: elastic_net_install_check.sql_in.log
>
>
> I am installing MADlib from source and concerned about the errors *madpack 
> ... install-check* reports. Here are the commands used:
> {code}
> apt install postgresql-server-dev-9.6
> apt install postgresql-plpython-9.6
> apt install cmake g++ libkrb5-dev m4 libboost-dev
> git clone https://github.com/apache/incubator-madlib
> cd incubator-madlib
> ./configure
> cd build/
> make
> make install
> src/bin/madpack -s madlib -c postgres/*@localhost/revit -p postgres install
> ...
> ...
> ...
> madpack.py : INFO : MADlib 1.10.0 installed successfully in MADLIB schema.
> {code}
> Next I run *madpack ... install-check* but it fails. Should I be concerned or 
> is this possibly a bug? See attached log file:
> {code}
> root@pg203:/home/john/incubator-madlib/build# src/bin/madpack -s madlib -c 
> postgres/*@localhost/revit -p postgres install-check
> madpack.py : INFO : Detected PostgreSQL version 9.6.
> TEST CASE RESULT|Module: array_ops|array_ops.sql_in|PASS|Time: 303 
> milliseconds
> TEST CASE RESULT|Module: bayes|gaussian_naive_bayes.sql_in|PASS|Time: 862 
> milliseconds
> TEST CASE RESULT|Module: bayes|bayes.sql_in|PASS|Time: 2674 milliseconds
> TEST CASE RESULT|Module: crf|crf_train_small.sql_in|PASS|Time: 1725 
> milliseconds
> TEST CASE RESULT|Module: crf|crf_train_large.sql_in|PASS|Time: 2920 
> milliseconds
> TEST CASE RESULT|Module: crf|crf_test_small.sql_in|PASS|Time: 1377 
> milliseconds
> TEST CASE RESULT|Module: crf|crf_test_large.sql_in|PASS|Time: 1470 
> milliseconds
> madpack.py : ERROR : Failed executing 
> /tmp/madlib.erAH0G/elastic_net/test/elastic_net_install_check.sql_in.tmp
> madpack.py : ERROR : Check the log at 
> /tmp/madlib.erAH0G/elastic_net/test/elastic_net_install_check.sql_in.log
> TEST CASE RESULT|Module: 
> elastic_net|elastic_net_install_check.sql_in|FAIL|Time: 522 milliseconds
> madpack.py : ERROR : SQL command failed:
> SQL: DROP SCHEMA IF EXISTS madlib_installcheck_elastic_net CASCADE;
> psql: could not connect to server: Connection refused
> Is the server running on host "localhost" (::1) and accepting
> TCP/IP connections on port 5432?
> FATAL:  the database system is in recovery mode
> FATAL:  the database system is in recovery mode
> Traceback (most recent call last):
>   File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py", 
> line 1574, in 
> main(sys.argv[1:])
>   File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py", 
> line 1505, in main
> _internal_run_query("DROP SCHEMA IF EXISTS %s CASCADE;" % (test_schema), 
> True)
>   File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py", 
> line 182, in _internal_run_query
> return run_query(sql, show_error, con_args)
>   File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py", 
> line 147, in run_query
> raise Exception
> Exception
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MADLIB-1145) Ubuntu 16.04 - Using GCC 5 (default gcc) causes Postgres 9.6 crash

[Ed Espino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MADLIB-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino updated MADLIB-1145:
--
Summary: Ubuntu 16.04 - Using GCC 5 (default gcc) causes Postgres 9.6 crash 
 (was: Ubuntu 16.04 - Using GCC 5 (default gcc) causes crashes)

> Ubuntu 16.04 - Using GCC 5 (default gcc) causes Postgres 9.6 crash
> --
>
> Key: MADLIB-1145
> URL: https://issues.apache.org/jira/browse/MADLIB-1145
> Project: Apache MADlib
>  Issue Type: Bug
>  Components: Build System
>Reporter: Ed Espino
>
> Upon analysis of MADLIB-1068, it was determined that the GCC 5 compiler which 
> is available on Ubuntu 16.04 causes MADlib to produce a Postgres 9.6 crash. 
> This JIRA will capture the GCC 5 issues.
> Please refer to Ubuntu 16.04 MADLIB-1068 for crash details and the workaround 
> (use GCC 4).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MADLIB-1145) Ubuntu 16.04 - Using GCC 5 (default gcc) causes crashes

[Ed Espino (JIRA)]

Ed Espino created MADLIB-1145:
-

 Summary: Ubuntu 16.04 - Using GCC 5 (default gcc) causes crashes
 Key: MADLIB-1145
 URL: https://issues.apache.org/jira/browse/MADLIB-1145
 Project: Apache MADlib
  Issue Type: Bug
  Components: Build System
Reporter: Ed Espino


Upon analysis of MADLIB-1068, it was determined that the GCC 5 compiler which 
is available on Ubuntu 16.04 causes MADlib to produce a Postgres 9.6 crash. 
This JIRA will capture the GCC 5 issues.

Please refer to Ubuntu 16.04 MADLIB-1068 for crash details and the workaround 
(use GCC 4).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MADLIB-1068) madpack install-check fails on PostgreSQL 9.6.2 & Ubuntu 16.04.2

[Ed Espino (JIRA)]

[ 
https://issues.apache.org/jira/browse/MADLIB-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16117111#comment-16117111
 ] 

Ed Espino commented on MADLIB-1068:
---

I managed to get MADlib's install-check to pass on Ubuntu 16.04. One thing that 
was nagging me was the issue was not seen on Ubuntu 14.04 (as reported in 
MADLIB-1068 by [~jhngrant]) and verified by me. On a hunch, I compared the 
compiler versions:

Ubuntu 16.04.3: gcc 5.4.0 (default installed via "apt-get install gcc g++")
Ubuntu 14.04: gcc 4.8.4 (default installed via "apt-get install gcc g++")

So on Ubuntu 16.04.3, I installed both gcc 4.8.5 ("apt-get install gcc-4.8 
g++-4.8") and gcc 4.9.3 ("apt-get install -y gcc-4.9 g++-4.9). I used the 
following base cmake command to use the gcc 4.* compilers:

CC=/usr/bin/gcc-4.8 CXX=/usr/bin/g++-4.8 cmake ..
CC=/usr/bin/gcc-4.9 CXX=/usr/bin/g++-4.9 cmake ..

I was able to build and run install-check using both compilers with 100% 
passing.

> madpack install-check fails on PostgreSQL 9.6.2 & Ubuntu 16.04.2
> 
>
> Key: MADLIB-1068
> URL: https://issues.apache.org/jira/browse/MADLIB-1068
> Project: Apache MADlib
>  Issue Type: Question
>  Components: Madpack
>Reporter: John Grant
>Assignee: Ed Espino
> Fix For: v1.12
>
> Attachments: elastic_net_install_check.sql_in.log
>
>
> I am installing MADlib from source and concerned about the errors *madpack 
> ... install-check* reports. Here are the commands used:
> {code}
> apt install postgresql-server-dev-9.6
> apt install postgresql-plpython-9.6
> apt install cmake g++ libkrb5-dev m4 libboost-dev
> git clone https://github.com/apache/incubator-madlib
> cd incubator-madlib
> ./configure
> cd build/
> make
> make install
> src/bin/madpack -s madlib -c postgres/*@localhost/revit -p postgres install
> ...
> ...
> ...
> madpack.py : INFO : MADlib 1.10.0 installed successfully in MADLIB schema.
> {code}
> Next I run *madpack ... install-check* but it fails. Should I be concerned or 
> is this possibly a bug? See attached log file:
> {code}
> root@pg203:/home/john/incubator-madlib/build# src/bin/madpack -s madlib -c 
> postgres/*@localhost/revit -p postgres install-check
> madpack.py : INFO : Detected PostgreSQL version 9.6.
> TEST CASE RESULT|Module: array_ops|array_ops.sql_in|PASS|Time: 303 
> milliseconds
> TEST CASE RESULT|Module: bayes|gaussian_naive_bayes.sql_in|PASS|Time: 862 
> milliseconds
> TEST CASE RESULT|Module: bayes|bayes.sql_in|PASS|Time: 2674 milliseconds
> TEST CASE RESULT|Module: crf|crf_train_small.sql_in|PASS|Time: 1725 
> milliseconds
> TEST CASE RESULT|Module: crf|crf_train_large.sql_in|PASS|Time: 2920 
> milliseconds
> TEST CASE RESULT|Module: crf|crf_test_small.sql_in|PASS|Time: 1377 
> milliseconds
> TEST CASE RESULT|Module: crf|crf_test_large.sql_in|PASS|Time: 1470 
> milliseconds
> madpack.py : ERROR : Failed executing 
> /tmp/madlib.erAH0G/elastic_net/test/elastic_net_install_check.sql_in.tmp
> madpack.py : ERROR : Check the log at 
> /tmp/madlib.erAH0G/elastic_net/test/elastic_net_install_check.sql_in.log
> TEST CASE RESULT|Module: 
> elastic_net|elastic_net_install_check.sql_in|FAIL|Time: 522 milliseconds
> madpack.py : ERROR : SQL command failed:
> SQL: DROP SCHEMA IF EXISTS madlib_installcheck_elastic_net CASCADE;
> psql: could not connect to server: Connection refused
> Is the server running on host "localhost" (::1) and accepting
> TCP/IP connections on port 5432?
> FATAL:  the database system is in recovery mode
> FATAL:  the database system is in recovery mode
> Traceback (most recent call last):
>   File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py", 
> line 1574, in 
> main(sys.argv[1:])
>   File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py", 
> line 1505, in main
> _internal_run_query("DROP SCHEMA IF EXISTS %s CASCADE;" % (test_schema), 
> True)
>   File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py", 
> line 182, in _internal_run_query
> return run_query(sql, show_error, con_args)
>   File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py", 
> line 147, in run_query
> raise Exception
> Exception
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MADLIB-1068) madpack install-check fails on PostgreSQL 9.6.2 & Ubuntu 16.04.2

[Ed Espino (JIRA)]

[ 
https://issues.apache.org/jira/browse/MADLIB-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114513#comment-16114513
 ] 

Ed Espino commented on MADLIB-1068:
---

I have identified a small test case which reproduces the issue in this 
environment (PostgreSQL 9.6.2, Ubuntu 16.04.3, MADlib master branch):

{code}
DROP TABLE IF EXISTS tbl_source, tbl_result;

CREATE TABLE tbl_source (id serial, x float8[], grp_by_col int, y float8);

INSERT INTO tbl_source(x, grp_by_col, y)
   VALUES ('{NULL, 0.04741, 0.00, 11.930, 0, 0.5730, 6.0300, 80.80, 2.5050, 
1, 273.0, 21.00, 396.90, 7.88}', 2, 11.90);

SELECT madlib.elastic_net_train('tbl_source',
'tbl_result',
'y',
'x',
'gaussian',
1,
0.2,
True,
NULL,
'fista',
'{eta = 2, max_stepsize = 0.5, use_active_set = 
f} 1',
NULL,
2000,
1e-6
   );
{code}


> madpack install-check fails on PostgreSQL 9.6.2 & Ubuntu 16.04.2
> 
>
> Key: MADLIB-1068
> URL: https://issues.apache.org/jira/browse/MADLIB-1068
> Project: Apache MADlib
>  Issue Type: Question
>  Components: Madpack
>Reporter: John Grant
>Assignee: Ed Espino
> Fix For: v1.12
>
> Attachments: elastic_net_install_check.sql_in.log
>
>
> I am installing MADlib from source and concerned about the errors *madpack 
> ... install-check* reports. Here are the commands used:
> {code}
> apt install postgresql-server-dev-9.6
> apt install postgresql-plpython-9.6
> apt install cmake g++ libkrb5-dev m4 libboost-dev
> git clone https://github.com/apache/incubator-madlib
> cd incubator-madlib
> ./configure
> cd build/
> make
> make install
> src/bin/madpack -s madlib -c postgres/*@localhost/revit -p postgres install
> ...
> ...
> ...
> madpack.py : INFO : MADlib 1.10.0 installed successfully in MADLIB schema.
> {code}
> Next I run *madpack ... install-check* but it fails. Should I be concerned or 
> is this possibly a bug? See attached log file:
> {code}
> root@pg203:/home/john/incubator-madlib/build# src/bin/madpack -s madlib -c 
> postgres/*@localhost/revit -p postgres install-check
> madpack.py : INFO : Detected PostgreSQL version 9.6.
> TEST CASE RESULT|Module: array_ops|array_ops.sql_in|PASS|Time: 303 
> milliseconds
> TEST CASE RESULT|Module: bayes|gaussian_naive_bayes.sql_in|PASS|Time: 862 
> milliseconds
> TEST CASE RESULT|Module: bayes|bayes.sql_in|PASS|Time: 2674 milliseconds
> TEST CASE RESULT|Module: crf|crf_train_small.sql_in|PASS|Time: 1725 
> milliseconds
> TEST CASE RESULT|Module: crf|crf_train_large.sql_in|PASS|Time: 2920 
> milliseconds
> TEST CASE RESULT|Module: crf|crf_test_small.sql_in|PASS|Time: 1377 
> milliseconds
> TEST CASE RESULT|Module: crf|crf_test_large.sql_in|PASS|Time: 1470 
> milliseconds
> madpack.py : ERROR : Failed executing 
> /tmp/madlib.erAH0G/elastic_net/test/elastic_net_install_check.sql_in.tmp
> madpack.py : ERROR : Check the log at 
> /tmp/madlib.erAH0G/elastic_net/test/elastic_net_install_check.sql_in.log
> TEST CASE RESULT|Module: 
> elastic_net|elastic_net_install_check.sql_in|FAIL|Time: 522 milliseconds
> madpack.py : ERROR : SQL command failed:
> SQL: DROP SCHEMA IF EXISTS madlib_installcheck_elastic_net CASCADE;
> psql: could not connect to server: Connection refused
> Is the server running on host "localhost" (::1) and accepting
> TCP/IP connections on port 5432?
> FATAL:  the database system is in recovery mode
> FATAL:  the database system is in recovery mode
> Traceback (most recent call last):
>   File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py", 
> line 1574, in 
> main(sys.argv[1:])
>   File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py", 
> line 1505, in main
> _internal_run_query("DROP SCHEMA IF EXISTS %s CASCADE;" % (test_schema), 
> True)
>   File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py", 
> line 182, in _internal_run_query
> return run_query(sql, show_error, con_args)
>   File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py", 
> line 147, in run_query
> raise Exception
> Exception
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MADLIB-1068) madpack install-check fails on PostgreSQL 9.6.2 & Ubuntu 16.04.2

[Ed Espino (JIRA)]

[ 
https://issues.apache.org/jira/browse/MADLIB-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113716#comment-16113716
 ] 

Ed Espino commented on MADLIB-1068:
---

BTW: this issue is 100% repeatable in my configuration: 
ubuntu-16.04.3-desktop-amd64.iso, PostgreSQL 9.6.2 and MADlib master 
(dc0a88ba4fbd0327ab99638ddf79f04d0b18f94f).

> madpack install-check fails on PostgreSQL 9.6.2 & Ubuntu 16.04.2
> 
>
> Key: MADLIB-1068
> URL: https://issues.apache.org/jira/browse/MADLIB-1068
> Project: Apache MADlib
>  Issue Type: Question
>  Components: Madpack
>Reporter: John Grant
>Assignee: Ed Espino
> Fix For: v1.12
>
> Attachments: elastic_net_install_check.sql_in.log
>
>
> I am installing MADlib from source and concerned about the errors *madpack 
> ... install-check* reports. Here are the commands used:
> {code}
> apt install postgresql-server-dev-9.6
> apt install postgresql-plpython-9.6
> apt install cmake g++ libkrb5-dev m4 libboost-dev
> git clone https://github.com/apache/incubator-madlib
> cd incubator-madlib
> ./configure
> cd build/
> make
> make install
> src/bin/madpack -s madlib -c postgres/*@localhost/revit -p postgres install
> ...
> ...
> ...
> madpack.py : INFO : MADlib 1.10.0 installed successfully in MADLIB schema.
> {code}
> Next I run *madpack ... install-check* but it fails. Should I be concerned or 
> is this possibly a bug? See attached log file:
> {code}
> root@pg203:/home/john/incubator-madlib/build# src/bin/madpack -s madlib -c 
> postgres/*@localhost/revit -p postgres install-check
> madpack.py : INFO : Detected PostgreSQL version 9.6.
> TEST CASE RESULT|Module: array_ops|array_ops.sql_in|PASS|Time: 303 
> milliseconds
> TEST CASE RESULT|Module: bayes|gaussian_naive_bayes.sql_in|PASS|Time: 862 
> milliseconds
> TEST CASE RESULT|Module: bayes|bayes.sql_in|PASS|Time: 2674 milliseconds
> TEST CASE RESULT|Module: crf|crf_train_small.sql_in|PASS|Time: 1725 
> milliseconds
> TEST CASE RESULT|Module: crf|crf_train_large.sql_in|PASS|Time: 2920 
> milliseconds
> TEST CASE RESULT|Module: crf|crf_test_small.sql_in|PASS|Time: 1377 
> milliseconds
> TEST CASE RESULT|Module: crf|crf_test_large.sql_in|PASS|Time: 1470 
> milliseconds
> madpack.py : ERROR : Failed executing 
> /tmp/madlib.erAH0G/elastic_net/test/elastic_net_install_check.sql_in.tmp
> madpack.py : ERROR : Check the log at 
> /tmp/madlib.erAH0G/elastic_net/test/elastic_net_install_check.sql_in.log
> TEST CASE RESULT|Module: 
> elastic_net|elastic_net_install_check.sql_in|FAIL|Time: 522 milliseconds
> madpack.py : ERROR : SQL command failed:
> SQL: DROP SCHEMA IF EXISTS madlib_installcheck_elastic_net CASCADE;
> psql: could not connect to server: Connection refused
> Is the server running on host "localhost" (::1) and accepting
> TCP/IP connections on port 5432?
> FATAL:  the database system is in recovery mode
> FATAL:  the database system is in recovery mode
> Traceback (most recent call last):
>   File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py", 
> line 1574, in 
> main(sys.argv[1:])
>   File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py", 
> line 1505, in main
> _internal_run_query("DROP SCHEMA IF EXISTS %s CASCADE;" % (test_schema), 
> True)
>   File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py", 
> line 182, in _internal_run_query
> return run_query(sql, show_error, con_args)
>   File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py", 
> line 147, in run_query
> raise Exception
> Exception
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MADLIB-1068) madpack install-check fails on PostgreSQL 9.6.2 & Ubuntu 16.04.2

[Ed Espino (JIRA)]

[ 
https://issues.apache.org/jira/browse/MADLIB-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113714#comment-16113714
 ] 

Ed Espino commented on MADLIB-1068:
---

Coredump appears to be initiated from MADlib.  Here is the complete sequence to 
reproduce the issue along with core stack info:

{code}
espino@ubuntu:~/incubator-madlib$ /usr/local/madlib/bin/madpack -s madlib -p 
postgres install-check -t elastic_net
madpack.py : INFO : Detected PostgreSQL version 9.6.
TEST CASE RESULT|Module: 
elastic_net|elastic_net_install_check.sql_in|FAIL|Time: 394 milliseconds
madpack.py : ERROR : Failed executing 
/tmp/madlib.EI4akX/elastic_net/test/elastic_net_install_check.sql_in.tmp
madpack.py : ERROR : Check the log at 
/tmp/madlib.EI4akX/elastic_net/test/elastic_net_install_check.sql_in.log
madpack.py : ERROR : SQL command failed:
SQL: DROP SCHEMA IF EXISTS madlib_installcheck_elastic_net CASCADE;
psql: FATAL:  the database system is in recovery mode

Traceback (most recent call last):
  File "/usr/local/madlib/Versions/1.12-dev/bin/../madpack/madpack.py", line 
1580, in 
main(sys.argv[1:])
  File "/usr/local/madlib/Versions/1.12-dev/bin/../madpack/madpack.py", line 
1511, in main
_internal_run_query("DROP SCHEMA IF EXISTS %s CASCADE;" % (test_schema), 
True)
  File "/usr/local/madlib/Versions/1.12-dev/bin/../madpack/madpack.py", line 
182, in _internal_run_query
return run_query(sql, show_error, con_args)
  File "/usr/local/madlib/Versions/1.12-dev/bin/../madpack/madpack.py", line 
147, in run_query
raise Exception
Exception
espino@ubuntu:~/incubator-madlib$ tail 
/tmp/madlib.EI4akX/elastic_net/test/elastic_net_install_check.sql_in.log
end;
$$ language plpgsql volatile;
CREATE FUNCTION
select check_elastic_net();
psql:/tmp/madlib.EI4akX/elastic_net/test/elastic_net_install_check.sql_in.tmp:822:
 NOTICE:  table "house_en" does not exist, skipping
psql:/tmp/madlib.EI4akX/elastic_net/test/elastic_net_install_check.sql_in.tmp:822:
 NOTICE:  table "house_en_summary" does not exist, skipping
psql:/tmp/madlib.EI4akX/elastic_net/test/elastic_net_install_check.sql_in.tmp:822:
 server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
psql:/tmp/madlib.EI4akX/elastic_net/test/elastic_net_install_check.sql_in.tmp:822:
 connection to server was lost
espino@ubuntu:~/incubator-madlib$ file ~/pgdata/core
/home/espino/pgdata/core: ELF 64-bit LSB core file x86-64, version 1 (SYSV), 
SVR4-style, from 'postgres: espino madlibtest 127.0.0.1(43184) SELECT'
espino@ubuntu:~/incubator-madlib$ gdb /usr/local/pgsql/bin/postgres
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/local/pgsql/bin/postgres...done.
(gdb) core ~/pgdata/core
[New LWP 101937]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `postgres: espino madlibtest 127.0.0.1(43184) SELECT '.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  pfree (pointer=0x51) at mcxt.c:1007
1007context = ((StandardChunkHeader *)
(gdb) set pagination off
(gdb) where
#0  pfree (pointer=0x51) at mcxt.c:1007
#1  0x7f534f16ac9d in 
madlib::dbconnector::postgres::Allocator::free<(madlib::dbal::MemoryContext)0> 
(inPtr=inPtr@entry=0x1db8c10, this=) at 
/home/espino/incubator-madlib/src/ports/postgres/dbconnector/Allocator_impl.hpp:189
#2  0x7f534f16afdd in operator delete[] (ptr=0x1db8c10) at 
/home/espino/incubator-madlib/src/ports/postgres/dbconnector/NewDelete.cpp:67
#3  0x7f534eebb112 in __gnu_cxx::new_allocator::deallocate 
(this=0x7fff5028bb30, __p=) at 
/usr/include/c++/5/ext/new_allocator.h:110
#4  __gnu_cxx::__alloc_traits::deallocate (__a=..., 
__n=, __p=) at 
/usr/include/c++/5/ext/alloc_traits.h:185
#5  std::__cxx11::basic_string::_M_destroy (__size=, 
this=0x7fff5028bb30) at /usr/include/c++/5/bits/basic_string.h:185
#6  std::__cxx11::basic_string::_M_dispose (this=0x7fff5028bb30) at 
/usr/include/c++/5/bits/basic_string.h:180
#7  std::__cxx11::basic_string

[jira] [Commented] (MADLIB-1068) madpack install-check fails on PostgreSQL 9.6.2 & Ubuntu 16.04.2

[Ed Espino (JIRA)]

[ 
https://issues.apache.org/jira/browse/MADLIB-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113646#comment-16113646
 ] 

Ed Espino commented on MADLIB-1068:
---

First attempt to reproduce the problem ... BINGO! Details of coredump coming ...

{code}
espino@ubuntu:~/incubator-madlib$ /usr/local/madlib/bin/madpack -s madlib -p 
postgres install-check
madpack.py : INFO : Detected PostgreSQL version 9.6.
TEST CASE RESULT|Module: array_ops|array_ops.sql_in|PASS|Time: 68 milliseconds
TEST CASE RESULT|Module: bayes|gaussian_naive_bayes.sql_in|PASS|Time: 105 
milliseconds
TEST CASE RESULT|Module: bayes|bayes.sql_in|PASS|Time: 198 milliseconds
TEST CASE RESULT|Module: crf|crf_train_small.sql_in|PASS|Time: 178 milliseconds
TEST CASE RESULT|Module: crf|crf_train_large.sql_in|PASS|Time: 413 milliseconds
TEST CASE RESULT|Module: crf|crf_test_small.sql_in|PASS|Time: 129 milliseconds
TEST CASE RESULT|Module: crf|crf_test_large.sql_in|PASS|Time: 149 milliseconds
TEST CASE RESULT|Module: 
elastic_net|elastic_net_install_check.sql_in|FAIL|Time: 205 milliseconds
madpack.py : ERROR : Failed executing 
/tmp/madlib.dbbSPO/elastic_net/test/elastic_net_install_check.sql_in.tmp
madpack.py : ERROR : Check the log at 
/tmp/madlib.dbbSPO/elastic_net/test/elastic_net_install_check.sql_in.log
madpack.py : ERROR : SQL command failed:
SQL: DROP SCHEMA IF EXISTS madlib_installcheck_elastic_net CASCADE;
psql: FATAL:  the database system is in recovery mode

Traceback (most recent call last):
  File "/usr/local/madlib/Versions/1.12-dev/bin/../madpack/madpack.py", line 
1580, in 
main(sys.argv[1:])
  File "/usr/local/madlib/Versions/1.12-dev/bin/../madpack/madpack.py", line 
1511, in main
_internal_run_query("DROP SCHEMA IF EXISTS %s CASCADE;" % (test_schema), 
True)
  File "/usr/local/madlib/Versions/1.12-dev/bin/../madpack/madpack.py", line 
182, in _internal_run_query
return run_query(sql, show_error, con_args)
  File "/usr/local/madlib/Versions/1.12-dev/bin/../madpack/madpack.py", line 
147, in run_query
raise Exception
Exception
{code}

> madpack install-check fails on PostgreSQL 9.6.2 & Ubuntu 16.04.2
> 
>
> Key: MADLIB-1068
> URL: https://issues.apache.org/jira/browse/MADLIB-1068
> Project: Apache MADlib
>  Issue Type: Question
>  Components: Madpack
>Reporter: John Grant
>Assignee: Ed Espino
> Fix For: v1.12
>
> Attachments: elastic_net_install_check.sql_in.log
>
>
> I am installing MADlib from source and concerned about the errors *madpack 
> ... install-check* reports. Here are the commands used:
> {code}
> apt install postgresql-server-dev-9.6
> apt install postgresql-plpython-9.6
> apt install cmake g++ libkrb5-dev m4 libboost-dev
> git clone https://github.com/apache/incubator-madlib
> cd incubator-madlib
> ./configure
> cd build/
> make
> make install
> src/bin/madpack -s madlib -c postgres/*@localhost/revit -p postgres install
> ...
> ...
> ...
> madpack.py : INFO : MADlib 1.10.0 installed successfully in MADLIB schema.
> {code}
> Next I run *madpack ... install-check* but it fails. Should I be concerned or 
> is this possibly a bug? See attached log file:
> {code}
> root@pg203:/home/john/incubator-madlib/build# src/bin/madpack -s madlib -c 
> postgres/*@localhost/revit -p postgres install-check
> madpack.py : INFO : Detected PostgreSQL version 9.6.
> TEST CASE RESULT|Module: array_ops|array_ops.sql_in|PASS|Time: 303 
> milliseconds
> TEST CASE RESULT|Module: bayes|gaussian_naive_bayes.sql_in|PASS|Time: 862 
> milliseconds
> TEST CASE RESULT|Module: bayes|bayes.sql_in|PASS|Time: 2674 milliseconds
> TEST CASE RESULT|Module: crf|crf_train_small.sql_in|PASS|Time: 1725 
> milliseconds
> TEST CASE RESULT|Module: crf|crf_train_large.sql_in|PASS|Time: 2920 
> milliseconds
> TEST CASE RESULT|Module: crf|crf_test_small.sql_in|PASS|Time: 1377 
> milliseconds
> TEST CASE RESULT|Module: crf|crf_test_large.sql_in|PASS|Time: 1470 
> milliseconds
> madpack.py : ERROR : Failed executing 
> /tmp/madlib.erAH0G/elastic_net/test/elastic_net_install_check.sql_in.tmp
> madpack.py : ERROR : Check the log at 
> /tmp/madlib.erAH0G/elastic_net/test/elastic_net_install_check.sql_in.log
> TEST CASE RESULT|Module: 
> elastic_net|elastic_net_install_check.sql_in|FAIL|Time: 522 milliseconds
> madpack.py : ERROR : SQL command failed:
> SQL: DROP SCHEMA IF EXISTS madlib_installcheck_elastic_net CASCADE;
> psql: could not connect to server: Connection refused
> Is the server running on host "localhost" (::1) and accepting
> TCP/IP connections on port 5432?
> FATAL:  the database system is in recovery mode
> FATAL:  the database system is in recovery mode
> Traceback (most recent call last):
>   File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py", 
> line 1574, in 
> 

[jira] [Commented] (MADLIB-1068) madpack install-check fails on PostgreSQL 9.6.2 & Ubuntu 16.04.2

[Ed Espino (JIRA)]

[ 
https://issues.apache.org/jira/browse/MADLIB-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113637#comment-16113637
 ] 

Ed Espino commented on MADLIB-1068:
---

I am trying to reproduce this issue using ubuntu-16.04.3-desktop-amd64.iso, 
PostgreSQL 9.6.2 and MADlib master branch.

> madpack install-check fails on PostgreSQL 9.6.2 & Ubuntu 16.04.2
> 
>
> Key: MADLIB-1068
> URL: https://issues.apache.org/jira/browse/MADLIB-1068
> Project: Apache MADlib
>  Issue Type: Question
>  Components: Madpack
>Reporter: John Grant
>Assignee: Ed Espino
> Fix For: v1.12
>
> Attachments: elastic_net_install_check.sql_in.log
>
>
> I am installing MADlib from source and concerned about the errors *madpack 
> ... install-check* reports. Here are the commands used:
> {code}
> apt install postgresql-server-dev-9.6
> apt install postgresql-plpython-9.6
> apt install cmake g++ libkrb5-dev m4 libboost-dev
> git clone https://github.com/apache/incubator-madlib
> cd incubator-madlib
> ./configure
> cd build/
> make
> make install
> src/bin/madpack -s madlib -c postgres/*@localhost/revit -p postgres install
> ...
> ...
> ...
> madpack.py : INFO : MADlib 1.10.0 installed successfully in MADLIB schema.
> {code}
> Next I run *madpack ... install-check* but it fails. Should I be concerned or 
> is this possibly a bug? See attached log file:
> {code}
> root@pg203:/home/john/incubator-madlib/build# src/bin/madpack -s madlib -c 
> postgres/*@localhost/revit -p postgres install-check
> madpack.py : INFO : Detected PostgreSQL version 9.6.
> TEST CASE RESULT|Module: array_ops|array_ops.sql_in|PASS|Time: 303 
> milliseconds
> TEST CASE RESULT|Module: bayes|gaussian_naive_bayes.sql_in|PASS|Time: 862 
> milliseconds
> TEST CASE RESULT|Module: bayes|bayes.sql_in|PASS|Time: 2674 milliseconds
> TEST CASE RESULT|Module: crf|crf_train_small.sql_in|PASS|Time: 1725 
> milliseconds
> TEST CASE RESULT|Module: crf|crf_train_large.sql_in|PASS|Time: 2920 
> milliseconds
> TEST CASE RESULT|Module: crf|crf_test_small.sql_in|PASS|Time: 1377 
> milliseconds
> TEST CASE RESULT|Module: crf|crf_test_large.sql_in|PASS|Time: 1470 
> milliseconds
> madpack.py : ERROR : Failed executing 
> /tmp/madlib.erAH0G/elastic_net/test/elastic_net_install_check.sql_in.tmp
> madpack.py : ERROR : Check the log at 
> /tmp/madlib.erAH0G/elastic_net/test/elastic_net_install_check.sql_in.log
> TEST CASE RESULT|Module: 
> elastic_net|elastic_net_install_check.sql_in|FAIL|Time: 522 milliseconds
> madpack.py : ERROR : SQL command failed:
> SQL: DROP SCHEMA IF EXISTS madlib_installcheck_elastic_net CASCADE;
> psql: could not connect to server: Connection refused
> Is the server running on host "localhost" (::1) and accepting
> TCP/IP connections on port 5432?
> FATAL:  the database system is in recovery mode
> FATAL:  the database system is in recovery mode
> Traceback (most recent call last):
>   File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py", 
> line 1574, in 
> main(sys.argv[1:])
>   File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py", 
> line 1505, in main
> _internal_run_query("DROP SCHEMA IF EXISTS %s CASCADE;" % (test_schema), 
> True)
>   File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py", 
> line 182, in _internal_run_query
> return run_query(sql, show_error, con_args)
>   File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py", 
> line 147, in run_query
> raise Exception
> Exception
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (MADLIB-1068) madpack install-check fails on PostgreSQL 9.6.2 & Ubuntu 16.04.2

[Ed Espino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MADLIB-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino reassigned MADLIB-1068:
-

Assignee: Ed Espino

> madpack install-check fails on PostgreSQL 9.6.2 & Ubuntu 16.04.2
> 
>
> Key: MADLIB-1068
> URL: https://issues.apache.org/jira/browse/MADLIB-1068
> Project: Apache MADlib
>  Issue Type: Question
>  Components: Madpack
>Reporter: John Grant
>Assignee: Ed Espino
> Fix For: v1.12
>
> Attachments: elastic_net_install_check.sql_in.log
>
>
> I am installing MADlib from source and concerned about the errors *madpack 
> ... install-check* reports. Here are the commands used:
> {code}
> apt install postgresql-server-dev-9.6
> apt install postgresql-plpython-9.6
> apt install cmake g++ libkrb5-dev m4 libboost-dev
> git clone https://github.com/apache/incubator-madlib
> cd incubator-madlib
> ./configure
> cd build/
> make
> make install
> src/bin/madpack -s madlib -c postgres/*@localhost/revit -p postgres install
> ...
> ...
> ...
> madpack.py : INFO : MADlib 1.10.0 installed successfully in MADLIB schema.
> {code}
> Next I run *madpack ... install-check* but it fails. Should I be concerned or 
> is this possibly a bug? See attached log file:
> {code}
> root@pg203:/home/john/incubator-madlib/build# src/bin/madpack -s madlib -c 
> postgres/*@localhost/revit -p postgres install-check
> madpack.py : INFO : Detected PostgreSQL version 9.6.
> TEST CASE RESULT|Module: array_ops|array_ops.sql_in|PASS|Time: 303 
> milliseconds
> TEST CASE RESULT|Module: bayes|gaussian_naive_bayes.sql_in|PASS|Time: 862 
> milliseconds
> TEST CASE RESULT|Module: bayes|bayes.sql_in|PASS|Time: 2674 milliseconds
> TEST CASE RESULT|Module: crf|crf_train_small.sql_in|PASS|Time: 1725 
> milliseconds
> TEST CASE RESULT|Module: crf|crf_train_large.sql_in|PASS|Time: 2920 
> milliseconds
> TEST CASE RESULT|Module: crf|crf_test_small.sql_in|PASS|Time: 1377 
> milliseconds
> TEST CASE RESULT|Module: crf|crf_test_large.sql_in|PASS|Time: 1470 
> milliseconds
> madpack.py : ERROR : Failed executing 
> /tmp/madlib.erAH0G/elastic_net/test/elastic_net_install_check.sql_in.tmp
> madpack.py : ERROR : Check the log at 
> /tmp/madlib.erAH0G/elastic_net/test/elastic_net_install_check.sql_in.log
> TEST CASE RESULT|Module: 
> elastic_net|elastic_net_install_check.sql_in|FAIL|Time: 522 milliseconds
> madpack.py : ERROR : SQL command failed:
> SQL: DROP SCHEMA IF EXISTS madlib_installcheck_elastic_net CASCADE;
> psql: could not connect to server: Connection refused
> Is the server running on host "localhost" (::1) and accepting
> TCP/IP connections on port 5432?
> FATAL:  the database system is in recovery mode
> FATAL:  the database system is in recovery mode
> Traceback (most recent call last):
>   File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py", 
> line 1574, in 
> main(sys.argv[1:])
>   File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py", 
> line 1505, in main
> _internal_run_query("DROP SCHEMA IF EXISTS %s CASCADE;" % (test_schema), 
> True)
>   File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py", 
> line 182, in _internal_run_query
> return run_query(sql, show_error, con_args)
>   File "/home/john/incubator-madlib/build/src/bin/../madpack/madpack.py", 
> line 147, in run_query
> raise Exception
> Exception
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (MADLIB-1093) Update build from source wiki section with cmake version

[Ed Espino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MADLIB-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino resolved MADLIB-1093.
---
Resolution: Fixed

A note has been added to the wiki.

> Update build from source wiki section with cmake version
> 
>
> Key: MADLIB-1093
> URL: https://issues.apache.org/jira/browse/MADLIB-1093
> Project: Apache MADlib
>  Issue Type: Documentation
>  Components: Documentation
>Reporter: Kyle R Dunn
>Assignee: Ed Espino
>Priority: Minor
> Fix For: v1.12
>
>
> When trying to build on CentOS 6 and using the ancient version of cmake from 
> yum, I encounter the following failure from cmake. 
> We should update the wiki page to reflect the minimum version (or the version 
> used in CI) to prevent others from having this issue.
> {code}
> [gpadmin@gpdb-sandbox build]$ cmake ..
> -- Could NOT find Boost
> -- No sufficiently recent version (>= 1.47) of Boost was found. Will download.
> -- Found PythonInterp: /usr/local/greenplum-db/ext/python/bin/python (found 
> version "2.6.2")
> -- Could NOT find PostgreSQL (missing:  POSTGRESQL_EXECUTABLE)
> -- Found Greenplum: /usr/local/greenplum-db-4.3.12.0/bin/postgres
> -- Found Greenplum_4_3ORCA: /usr/local/greenplum-db-4.3.12.0/bin/postgres
> >> Adding Greenplum 4.3ORCA (x86_64) to target list...
> -- Could NOT find HAWQ (missing:  HAWQ_EXECUTABLE)
> Segmentation fault (core dumped)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (MADLIB-1144) Remove DISCLAIMER file once MADlib registered trademark has been fully transferred to ASF.

[Ed Espino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MADLIB-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino reassigned MADLIB-1144:
-

Assignee: Ed Espino

> Remove DISCLAIMER file once MADlib registered trademark has been fully 
> transferred to ASF.
> --
>
> Key: MADLIB-1144
> URL: https://issues.apache.org/jira/browse/MADLIB-1144
> Project: Apache MADlib
>  Issue Type: Task
>Reporter: Ed Espino
>Assignee: Ed Espino
>
> Post TLP graduation activities, we will be retaining the DISCLAIMER file 
> referencing the MADlib trademark transition activity noted in 
> PODLINGNAMESEARCH-125. This task will be used to track the removal of the 
> DISCLAIMER file once the trademark is fully transferred to ASF.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MADLIB-1144) Remove DISCLAIMER file once MADlib registered trademark has been fully transferred to ASF.

[Ed Espino (JIRA)]

Ed Espino created MADLIB-1144:
-

 Summary: Remove DISCLAIMER file once MADlib registered trademark 
has been fully transferred to ASF.
 Key: MADLIB-1144
 URL: https://issues.apache.org/jira/browse/MADLIB-1144
 Project: Apache MADlib
  Issue Type: Task
Reporter: Ed Espino


Post TLP graduation activities, we will be retaining the DISCLAIMER file 
referencing the MADlib trademark transition activity noted in 
PODLINGNAMESEARCH-125. This task will be used to track the removal of the 
DISCLAIMER file once the trademark is fully transferred to ASF.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MADLIB-1093) Update build from source wiki section with cmake version

[Ed Espino (JIRA)]

[ 
https://issues.apache.org/jira/browse/MADLIB-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16111934#comment-16111934
 ] 

Ed Espino commented on MADLIB-1093:
---

I have requested write access to wiki so I can add a note about the possible 
cmake interference by the gpdb greenplum_path.sh file.

> Update build from source wiki section with cmake version
> 
>
> Key: MADLIB-1093
> URL: https://issues.apache.org/jira/browse/MADLIB-1093
> Project: Apache MADlib
>  Issue Type: Documentation
>  Components: Documentation
>Reporter: Kyle R Dunn
>Assignee: Ed Espino
>Priority: Minor
> Fix For: v1.12
>
>
> When trying to build on CentOS 6 and using the ancient version of cmake from 
> yum, I encounter the following failure from cmake. 
> We should update the wiki page to reflect the minimum version (or the version 
> used in CI) to prevent others from having this issue.
> {code}
> [gpadmin@gpdb-sandbox build]$ cmake ..
> -- Could NOT find Boost
> -- No sufficiently recent version (>= 1.47) of Boost was found. Will download.
> -- Found PythonInterp: /usr/local/greenplum-db/ext/python/bin/python (found 
> version "2.6.2")
> -- Could NOT find PostgreSQL (missing:  POSTGRESQL_EXECUTABLE)
> -- Found Greenplum: /usr/local/greenplum-db-4.3.12.0/bin/postgres
> -- Found Greenplum_4_3ORCA: /usr/local/greenplum-db-4.3.12.0/bin/postgres
> >> Adding Greenplum 4.3ORCA (x86_64) to target list...
> -- Could NOT find HAWQ (missing:  HAWQ_EXECUTABLE)
> Segmentation fault (core dumped)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MADLIB-1093) Update build from source wiki section with cmake version

[Ed Espino (JIRA)]

[ 
https://issues.apache.org/jira/browse/MADLIB-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16111868#comment-16111868
 ] 

Ed Espino commented on MADLIB-1093:
---

BTW: What helped identify the issue was I could not reproduce the issue in a 
clean docker container environment. I this environment I had not sourced the 
greenplum_path.sh file. The "cmake --version" command in the gpdb-sandbox 
provided references to "/usr/local/greenplum-db/./lib/libxml2.so.2" which 
indicated something in the user's environment was adding this non-standard 
share library location to the environment.

> Update build from source wiki section with cmake version
> 
>
> Key: MADLIB-1093
> URL: https://issues.apache.org/jira/browse/MADLIB-1093
> Project: Apache MADlib
>  Issue Type: Documentation
>  Components: Documentation
>Reporter: Kyle R Dunn
>Assignee: Ed Espino
>Priority: Minor
> Fix For: v1.12
>
>
> When trying to build on CentOS 6 and using the ancient version of cmake from 
> yum, I encounter the following failure from cmake. 
> We should update the wiki page to reflect the minimum version (or the version 
> used in CI) to prevent others from having this issue.
> {code}
> [gpadmin@gpdb-sandbox build]$ cmake ..
> -- Could NOT find Boost
> -- No sufficiently recent version (>= 1.47) of Boost was found. Will download.
> -- Found PythonInterp: /usr/local/greenplum-db/ext/python/bin/python (found 
> version "2.6.2")
> -- Could NOT find PostgreSQL (missing:  POSTGRESQL_EXECUTABLE)
> -- Found Greenplum: /usr/local/greenplum-db-4.3.12.0/bin/postgres
> -- Found Greenplum_4_3ORCA: /usr/local/greenplum-db-4.3.12.0/bin/postgres
> >> Adding Greenplum 4.3ORCA (x86_64) to target list...
> -- Could NOT find HAWQ (missing:  HAWQ_EXECUTABLE)
> Segmentation fault (core dumped)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (MADLIB-1093) Update build from source wiki section with cmake version

[Ed Espino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MADLIB-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino updated MADLIB-1093:
--
Component/s: Documentation

> Update build from source wiki section with cmake version
> 
>
> Key: MADLIB-1093
> URL: https://issues.apache.org/jira/browse/MADLIB-1093
> Project: Apache MADlib
>  Issue Type: Documentation
>  Components: Documentation
>Reporter: Kyle R Dunn
>Assignee: Ed Espino
>Priority: Minor
> Fix For: v1.12
>
>
> When trying to build on CentOS 6 and using the ancient version of cmake from 
> yum, I encounter the following failure from cmake. 
> We should update the wiki page to reflect the minimum version (or the version 
> used in CI) to prevent others from having this issue.
> {code}
> [gpadmin@gpdb-sandbox build]$ cmake ..
> -- Could NOT find Boost
> -- No sufficiently recent version (>= 1.47) of Boost was found. Will download.
> -- Found PythonInterp: /usr/local/greenplum-db/ext/python/bin/python (found 
> version "2.6.2")
> -- Could NOT find PostgreSQL (missing:  POSTGRESQL_EXECUTABLE)
> -- Found Greenplum: /usr/local/greenplum-db-4.3.12.0/bin/postgres
> -- Found Greenplum_4_3ORCA: /usr/local/greenplum-db-4.3.12.0/bin/postgres
> >> Adding Greenplum 4.3ORCA (x86_64) to target list...
> -- Could NOT find HAWQ (missing:  HAWQ_EXECUTABLE)
> Segmentation fault (core dumped)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (MADLIB-1093) Update build from source wiki section with cmake version

[Ed Espino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MADLIB-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino reassigned MADLIB-1093:
-

Assignee: Ed Espino

> Update build from source wiki section with cmake version
> 
>
> Key: MADLIB-1093
> URL: https://issues.apache.org/jira/browse/MADLIB-1093
> Project: Apache MADlib
>  Issue Type: Documentation
>Reporter: Kyle R Dunn
>Assignee: Ed Espino
>Priority: Minor
> Fix For: v1.12
>
>
> When trying to build on CentOS 6 and using the ancient version of cmake from 
> yum, I encounter the following failure from cmake. 
> We should update the wiki page to reflect the minimum version (or the version 
> used in CI) to prevent others from having this issue.
> {code}
> [gpadmin@gpdb-sandbox build]$ cmake ..
> -- Could NOT find Boost
> -- No sufficiently recent version (>= 1.47) of Boost was found. Will download.
> -- Found PythonInterp: /usr/local/greenplum-db/ext/python/bin/python (found 
> version "2.6.2")
> -- Could NOT find PostgreSQL (missing:  POSTGRESQL_EXECUTABLE)
> -- Found Greenplum: /usr/local/greenplum-db-4.3.12.0/bin/postgres
> -- Found Greenplum_4_3ORCA: /usr/local/greenplum-db-4.3.12.0/bin/postgres
> >> Adding Greenplum 4.3ORCA (x86_64) to target list...
> -- Could NOT find HAWQ (missing:  HAWQ_EXECUTABLE)
> Segmentation fault (core dumped)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MADLIB-1142) TLP graduation - Update Jenkins build projects

[Ed Espino (JIRA)]

[ 
https://issues.apache.org/jira/browse/MADLIB-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16111379#comment-16111379
 ] 

Ed Espino commented on MADLIB-1142:
---

If we settle on the repository name (minus .git suffix) for the check out 
sub-directory name, a corresponding shell script change can be made to the 
jenkins_build.sh and rat_check.sh scripts.

> TLP graduation - Update Jenkins build projects
> --
>
> Key: MADLIB-1142
> URL: https://issues.apache.org/jira/browse/MADLIB-1142
> Project: Apache MADlib
>  Issue Type: Task
>  Components: Build System
>Reporter: Ed Espino
> Fix For: v1.12
>
>
> The following Jenkins build projects will need to be updated:
> * https://builds.apache.org/view/M-R/view/MADlib/job/madlib-master-build/
> * https://builds.apache.org/view/M-R/view/MADlib/job/madlib-pr-build/
> The "Check out to a sub-directory" value will need to be updated to reflect 
> the "repository" name (from: incubator-madlib to: madlib) once the repository 
> is officially changed. This will also allow the following to be added as the 
> build command for each project (removing the hard coded references). This 
> will also allow the jenkins_build.sh and rat_check.sh scripts to dynamically 
> determine where the source is located for the builds.
> {code}
> REPONAME=$(basename ${GIT_URL} .git)
> echo "REPONAME: ${REPONAME}"
> /bin/bash ./${REPONAME}/tool/jenkins/jenkins_build.sh
> /bin/bash ./${REPONAME}/tool/jenkins/rat_check.sh
> mkdir -p ${WORKSPACE}/logs/target
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MADLIB-1142) TLP graduation - Update Jenkins build projects

[Ed Espino (JIRA)]

Ed Espino created MADLIB-1142:
-

 Summary: TLP graduation - Update Jenkins build projects
 Key: MADLIB-1142
 URL: https://issues.apache.org/jira/browse/MADLIB-1142
 Project: Apache MADlib
  Issue Type: Task
  Components: Build System
Reporter: Ed Espino
 Fix For: v1.12


The following Jenkins build projects will need to be updated:
* https://builds.apache.org/view/M-R/view/MADlib/job/madlib-master-build/
* https://builds.apache.org/view/M-R/view/MADlib/job/madlib-pr-build/

The "Check out to a sub-directory" value will need to be updated to reflect the 
"repository" name (from: incubator-madlib to: madlib) once the repository is 
officially changed. This will also allow the following to be added as the build 
command for each project (removing the hard coded references). This will also 
allow the jenkins_build.sh and rat_check.sh scripts to dynamically determine 
where the source is located for the builds.

{code}
REPONAME=$(basename ${GIT_URL} .git)
echo "REPONAME: ${REPONAME}"

/bin/bash ./${REPONAME}/tool/jenkins/jenkins_build.sh
/bin/bash ./${REPONAME}/tool/jenkins/rat_check.sh

mkdir -p ${WORKSPACE}/logs/target
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (MADLIB-1133) TLP graduation - remove references to "incubating" in source tree

[Ed Espino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MADLIB-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino reassigned MADLIB-1133:
-

Assignee: Ed Espino  (was: Frank McQuillan)

> TLP graduation  - remove references to "incubating" in source tree
> --
>
> Key: MADLIB-1133
> URL: https://issues.apache.org/jira/browse/MADLIB-1133
> Project: Apache MADlib
>  Issue Type: Task
>  Components: All Modules
>Reporter: Frank McQuillan
>Assignee: Ed Espino
>Priority: Minor
> Fix For: v1.12
>
>
>  Source tree incubation references. Run
>"ack -i incubat" 
> command on the master branch and make appropriate updates as per the output



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MADLIB-1133) TLP graduation - remove references to "incubating" in source tree

[Ed Espino (JIRA)]

[ 
https://issues.apache.org/jira/browse/MADLIB-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16109823#comment-16109823
 ] 

Ed Espino commented on MADLIB-1133:
---

Thanks [~okislal]. I have submitted [GitHub Pull Request 
#158|https://github.com/apache/incubator-madlib/pull/158]. Unfortunately, at 
the moment, I cannot assign this issue to myself.

> TLP graduation  - remove references to "incubating" in source tree
> --
>
> Key: MADLIB-1133
> URL: https://issues.apache.org/jira/browse/MADLIB-1133
> Project: Apache MADlib
>  Issue Type: Task
>  Components: All Modules
>Reporter: Frank McQuillan
>Assignee: Frank McQuillan
>Priority: Minor
> Fix For: v1.12
>
>
>  Source tree incubation references. Run
>"ack -i incubat" 
> command on the master branch and make appropriate updates as per the output



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (MADLIB-1133) TLP graduation - remove references to "incubating" in source tree

[Ed Espino (JIRA)]

[ 
https://issues.apache.org/jira/browse/MADLIB-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16109717#comment-16109717
 ] 

Ed Espino edited comment on MADLIB-1133 at 8/1/17 8:41 PM:
---

BTW: I have a branch 
(https://github.com/edespino/incubator-madlib/tree/MADLIB-1133) with changes 
for this task.


was (Author: espino):
BTW: I have a branch with changes for this task.

> TLP graduation  - remove references to "incubating" in source tree
> --
>
> Key: MADLIB-1133
> URL: https://issues.apache.org/jira/browse/MADLIB-1133
> Project: Apache MADlib
>  Issue Type: Task
>  Components: All Modules
>Reporter: Frank McQuillan
>Assignee: Frank McQuillan
>Priority: Minor
> Fix For: v1.12
>
>
>  Source tree incubation references. Run
>"ack -i incubat" 
> command on the master branch and make appropriate updates as per the output



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MADLIB-1133) TLP graduation - remove references to "incubating" in source tree

[Ed Espino (JIRA)]

[ 
https://issues.apache.org/jira/browse/MADLIB-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16109717#comment-16109717
 ] 

Ed Espino commented on MADLIB-1133:
---

BTW: I have a branch with changes for this task.

> TLP graduation  - remove references to "incubating" in source tree
> --
>
> Key: MADLIB-1133
> URL: https://issues.apache.org/jira/browse/MADLIB-1133
> Project: Apache MADlib
>  Issue Type: Task
>  Components: All Modules
>Reporter: Frank McQuillan
>Assignee: Frank McQuillan
>Priority: Minor
> Fix For: v1.12
>
>
>  Source tree incubation references. Run
>"ack -i incubat" 
> command on the master branch and make appropriate updates as per the output



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MADLIB-1133) TLP graduation - remove references to "incubating" in source tree

[Ed Espino (JIRA)]

[ 
https://issues.apache.org/jira/browse/MADLIB-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16109234#comment-16109234
 ] 

Ed Espino commented on MADLIB-1133:
---

Has any progress been taken for this task?

> TLP graduation  - remove references to "incubating" in source tree
> --
>
> Key: MADLIB-1133
> URL: https://issues.apache.org/jira/browse/MADLIB-1133
> Project: Apache MADlib
>  Issue Type: Task
>  Components: All Modules
>Reporter: Frank McQuillan
>Assignee: Frank McQuillan
>Priority: Minor
> Fix For: v1.12
>
>
>  Source tree incubation references. Run
>"ack -i incubat" 
> command on the master branch and make appropriate updates as per the output



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MADLIB-1138) Add basic code coverage support

[Ed Espino (JIRA)]

Ed Espino created MADLIB-1138:
-

 Summary: Add basic code coverage support
 Key: MADLIB-1138
 URL: https://issues.apache.org/jira/browse/MADLIB-1138
 Project: Apache MADlib
  Issue Type: Task
  Components: Build System
Reporter: Ed Espino


For developers, add cmake option configuration option ENABLE_COVERAGE which 
will introduce gcov compilation and linking options (-fprofile-arcs 
-ftest-coverage). Two supporting make targets are introduced:
* GenCoverageReport - Capture gcov counters and generate report
* ResetCoverageCounters - Zero counters gcov counters

Features:
* Counters will be captured in build/CodeCoverage.info file. System and Third 
party metrics will be filtered out of coverage info file and stored in 
CodeCoverage-filtered.info
* HTML report will be created in build/CodeCoverageReport directory

Usage:
* cmake -DENABLE_COVERAGE=ON ..
* 
* make GenCoverageReport
* 
* make ResetCoverageCounters
* 
* make GenCoverageReport



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)