JRedisClient-tests error

[SamPeng87]

JRedisClient-tests 94 1 0
testInfo Test class: org.jredis.ri.alphazero.JRedisClientTest
java.lang.AssertionError: expected object to not be null
at org.jredis.ri.alphazero.JRedisProviderTestsBase.testInfo(JRedisProviderTestsBase.java:3046)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:70)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:160)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:100)
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:115)
at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
... Removed 29 stack frames

what happen?

[alphazero]

You are not using the correct version of Redis. Read
redis_compliance.txt.

On Mon, 5 Mar 2012 22:51:13 -0800, SamPeng87 wrote:

JRedisClient-tests 94 1 0
testInfo Test class: org.jredis.ri.alphazero.JRedisClientTest
java.lang.AssertionError: expected object to not be null
at

org.jredis.ri.alphazero.JRedisProviderTestsBase.testInfo(JRedisProviderTestsBase.java:3046)
at

org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:70)
at

org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:160)
at

org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:100)
at

org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:115)
at

org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188)
at

org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
at

org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
at

org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
... Removed 29 stack frames

what happen?

---

Reply to this email directly or view it on GitHub:
#61

[alphazero]

FYI for anyone else with this issue: Tests for INFO are strictly looking for a few named values that were deprecated in later Redis versions. The test fails but it does not indicate error in the client (e.g. you can use it with that version of Redis) but to perfectly correct about matching client to Redis, refer to the top level redis_compliance.txt file.