Daniel Owen added a comment - 18/Nov/19 12:01 AM - edited Hi Anitha Kuberan Could you upload the logs? Do you have the last known working build? thanks

Dave Rigby added a comment - 18/Nov/19 1:32 AM Anitha Kuberan Please use the Bug Template when raising MBs - specifically what is the expected behaviour, and what is the actual behavour? In this instance, what should happen if you attempt to ask for a random key from a bucket which has no keys in it?

Daniel Owen added a comment - 18/Nov/19 9:54 AM Investigated running the test and see the following error when run against MH: Traceback (most recent call last): File "pytests/epengine/basic_ops.py", line 293, in do_get_random_key error.message)) AssertionError: <MemcachedError #1 ``Memcached error #1''> Tried on 6.0.1 and see the same error. The get_random_key functionality was fixed in MB-31495 In the associated patch we added the following test // Check that getRandomKey works correctly when given a random value of zero TEST_P(KVBucketParamTest, MB31495_GetRandomKey) { std::function<long()> returnZero = []() { return 0; }; setRandomFunction(returnZero);   // Try with am empty hash table auto gv = store->getRandomKey(); EXPECT_EQ(ENGINE_KEY_ENOENT, gv.getStatus());   Item item = store_item( vbid, {"key", DocNamespace::DefaultCollection}, "value", 0);   // Try with a non-empty hash table gv = store->getRandomKey(); EXPECT_EQ(ENGINE_SUCCESS, gv.getStatus()); } In the test we check that with an empty hash table (i.e. bucket with no docs) we return ENGINE_KEY_ENOENT. Therefore, I think the test might need updating to reflect this behaviour.

Dave Rigby added a comment - 05/Dec/19 3:49 AM Changing component to "test_execution" - the failure is due to the test having incorrect expectations on 6.5.

Anitha Kuberan added a comment - 12/Mar/20 8:19 PM changed the test script and script works fine.