Looks like we have some failing tests:

Failed tests:
  ITestRawIndexQuery.testBucketIndexHack:143 expected:<100> but was:<103>
  ITestSecondaryIndexQueryOp.testBucketIndexHack:540 null
  ITestDeleteOperation.testDeleteObjectTestType:46->testDeleteObject:73 expected:<{"value":"value"}> but was:<null>

How do you have your test-rig setup? Are we using the java-client branch of riak-client-tools?

This is from the buildbot tests

Attached is a zip from five test runs locally. Some were successful, some not.

gh-593-test-runs.zip

I wonder if oracle jdk would give different results.

Thanks,
Alex

On Feb 18, 2016, at 5:29 PM, Luke Bakken notifications@github.com wrote:

Attached is a zip from five test runs locally. Some were successful, some not.

gh-593-test-runs.zip

—
Reply to this email directly or view it on GitHub.

OK I'll give it a try.

Unfortunately ... some of the same errors. I had to CTRL-C the last test, frozen on:

Running com.basho.riak.client.core.operations.itest.ITestListKeysOperation

gh-593-oracle-test-runs.zip

@javajolt @lukebakken Ok, this one should be ready now too. Fixes include all the security / buildbot fixes from PR #595. This should include everything that you've noted in this review so far.

@alexmoore - is it worth making the changes to the tests at this point so the java-client branch in riak-client-tools can go away?

@lukebakken Now that we're using LevelDB as the default file system I think we can. I'd like to not stack anymore stuff into this cascade of PRs :/ I can start on that after we get these merged - I think I would need to change the bucket type names mostly, and then the other 80% unexpected work.

Great! Please to be shipping 👍