The first set of requirement fail to install at python’s unittest. That sort-of
stops me dead. Don’t have a lot of dedicated time right now to debug so I let
Travis do the tests and they are passing now and all comments are resolved. I
left the keystore in so we ca address in a separate Jira.
Resolved, passing in Travis now.
On Fri, Aug 12, 2016 at 3:04 PM, Pat Ferrel wrote:
> Alex, can you look at these unit test failures on the PR, they seem to be
> in JDBCPEvents
>
> https://travis-ci.org/apache/incubator-predictionio/builds/151905196
>
>
> On Aug 12,
Alex, can you look at these unit test failures on the PR, they seem to be in
JDBCPEvents
https://travis-ci.org/apache/incubator-predictionio/builds/151905196
On Aug 12, 2016, at 1:18 PM, Pat Ferrel wrote:
Can't install unittest with pip or pip3 even though the rest
Can't install unittest with pip or pip3 even though the rest of the
prerequisites work. Simply refuses to find it. Pip3 search unittest give this:
WebTestRunner (0.2)- Web-based interface for selectively
executing client-side Python UnitTests
unittest (0.0) -
With the keystore my template-based integration test passes and I’ve put the
keystore back in. The diffs on PRs on Github seem completely wonky right now.
Git diff is trustworthy at least.
Will try the python tests now too.
Thanks guys, working smoothly now.
On Aug 11, 2016, at 11:53 AM,
Hi all,
I went ahead and pulled Pat's branch, performed a clean build, and repeated
the quick start guide of the Scala parallel recommendation template. I
could produce the same problem, and root caused it to a missing
conf/keystore.jks file.
I think with SSL now optional, we should not be
I want to clarify some points:
2) Deploying templates do not require SSL. If you execute
./make-distribution.sh using the current develop branch (provided you
change the namespace in the template from io.prediction to
org.apache.predictionio), you can deploy without SSL on localhost. The
travis