Details
-
Bug
-
Resolution: Fixed
-
Test Blocker
-
Cheshire-Cat
-
Untriaged
-
1
-
Unknown
Description
Build: 7.0.0-2270
test:
./testrunner -i node_conf.ini -p get-cbcollect-info=True,get-couch-dbinfo=True,skip_cleanup=False -t eventing.eventing_curl.EventingCurl.test_curl_get,nodes_init=2,services_init=kv-eventing,dataset=default,reset_services=True,skip_cleanup=True,path=basic-auth,curl_user=postman,curl_password=password,auth_type=basic,curl=True
Error:
======================================================================
ERROR: test_curl_get (eventing.eventing_curl.EventingCurl)
----------------------------------------------------------------------
Traceback (most recent call last):
File "pytests/eventing/eventing_curl.py", line 59, in test_curl_get
self.verify_eventing_results(self.function_name, self.docs_per_day * 2016, skip_stats_validation=True)
File "./pytests/eventing/eventing_base.py", line 285, in verify_eventing_results
timers_in_past,lcb))
Exception: missing data in destination bucket. Current : 2012 Expected : 2016 dcp_backlog : 0 TIMERS_IN_PAST : 0 lcb_exceptions : {'172.23.120.59': {}}
======================================================================
ERROR: test_curl_get (eventing.eventing_curl.EventingCurl)
----------------------------------------------------------------------
Traceback (most recent call last):
File "pytests/eventing/eventing_curl.py", line 50, in tearDown
super(EventingCurl, self).tearDown()
File "./pytests/eventing/eventing_base.py", line 113, in tearDown
raise Exception("metdata bucket is not empty at the end of test")
Exception: metdata bucket is not empty at the end of test
----------------------------------------------------------------------
Ran 1 test in 918.707s
Not sure if this is a regression - 7.0.0-2267 is clean - but have seen this issue intermittently before - this time it has happened in all platforms except centos - please take a look and see if this is a testware issue - if it is a product bug, please assign to dev