[SPY-116] Spy test results failures through jenkins Created: 26/Mar/13  Updated: 03/Jun/13

Status: Open
Project: Spymemcached Java Client
Component/s: None
Affects Version/s: None
Fix Version/s: .next
Security Level: Public

Type: Bug Priority: Major
Reporter: Deepti Dawar Assignee: Michael Nitschinger
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File spy_jenkins_failures.png    

 Description   
The feature tests which are part of the spymemcached project encounter a lot many failures when run from jenkins.

Please have a look at the snapshot, but we need to investigate the root cause in detail.

 Comments   
Comment by Michael Nitschinger [ 08/May/13 ]
Hi deepti,

we need to run the standalone spy tests not against couchbase, but against a vanilla memcached installation. (http://memcached.org/)
Comment by Deepti Dawar [ 14/May/13 ]
Yes, its already connecting to the vanilla memcached client.
The property is already defined in the build.xml and hasn't been altered while running the jenkins job.

 <property name="server.port_number" value="11211"/>
Comment by Michael Nitschinger [ 29/May/13 ]
Does that now work all correct?
Comment by Michael Nitschinger [ 29/May/13 ]
for verification
Comment by Deepti Dawar [ 30/May/13 ]
No Michael. Its still having errors.
Generated at Tue Sep 02 12:01:08 CDT 2014 using JIRA 5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9.