-
Type: Improvement
-
Resolution: Fixed
-
Priority: Minor - P4
-
Affects Version/s: None
-
Component/s: Test Coverage
-
None
Remove MongoClientsSpecification.application_name_should_appear_in_the_system.profile_collection. It frequently fails with the following error:
FAILURE: Condition not satisfied: profileDocument.get('appName') == appName | | | | | null | appName1 | false [op:insert, ns:JavaDriverTest.com.mongodb.MongoClientSessionSpecification, command:[insert:com.mongodb.MongoClientSessionSpecification, ordered:true, writeConcern:[w:0], $db:JavaDriverTest], ninserted:1, keysInserted:1, numYield:0, locks:[ParallelBatchWriterMode:[acquireCount:[r:4]], ReplicationStateTransition:[acquireCount:[w:4]], Global:[acquireCount:[r:1, w:3]], Database:[acquireCount:[w:3], acquireWaitCount:[w:1], timeAcquiringMicros:[w:6114]], Collection:[acquireCount:[r:2, w:2, W:1]], Mutex:[acquireCount:[r:5]]], flowControl:[acquireCount:3], storage:[:], responseLength:0, protocol:op_msg, millis:27, ts:Fri Aug 23 14:53:36 UTC 2019, client:127.0.0.1, allUsers:[], user:] (org.spockframework.runtime.SpockComparisonFailure) Condition not satisfied: profileDocument.get('appName') == appName | | | | | null | appName1 | false [op:insert, ns:JavaDriverTest.com.mongodb.MongoClientSessionSpecification, command:[insert:com.mongodb.MongoClientSessionSpecification, ordered:true, writeConcern:[w:0], $db:JavaDriverTest], ninserted:1, keysInserted:1, numYield:0, locks:[ParallelBatchWriterMode:[acquireCount:[r:4]], ReplicationStateTransition:[acquireCount:[w:4]], Global:[acquireCount:[r:1, w:3]], Database:[acquireCount:[w:3], acquireWaitCount:[w:1], timeAcquiringMicros:[w:6114]], Collection:[acquireCount:[r:2, w:2, W:1]], Mutex:[acquireCount:[r:5]]], flowControl:[acquireCount:3], storage:[:], responseLength:0, protocol:op_msg, millis:27, ts:Fri Aug 23 14:53:36 UTC 2019, client:127.0.0.1, allUsers:[], user:] at com.mongodb.MongoClientsSpecification.application name should appear in the system.profile collection(MongoClientsSpecification.groovy:54) system-out: 14:53:36.007 [Test worker] INFO org.mongodb.driver.cluster - Cluster created with settings {hosts=[localhost:27017], mode=SINGLE, requiredClusterType=UNKNOWN, serverSelectionTimeout='30000 ms', maxWaitQueueSize=500} 14:53:36.008 [Test worker] INFO org.mongodb.driver.cluster - Cluster description not yet available. Waiting for 30000 ms before timing out 14:53:36.009 [cluster-ClusterId{value='5d5ffdf02629ce314422e7b1', description='null'}-localhost:27017] INFO org.mongodb.driver.connection - Opened connection [connectionId{localValue:668, serverValue:600}] to localhost:27017 14:53:36.009 [cluster-ClusterId{value='5d5ffdf02629ce314422e7b1', description='null'}-localhost:27017] INFO org.mongodb.driver.cluster - Monitor thread successfully connected to server with description ServerDescription{address=localhost:27017, type=STANDALONE, state=CONNECTED, ok=true, minWireVersion=0, maxWireVersion=8, maxDocumentSize=16777216, logicalSessionTimeoutMinutes=30, roundTripTimeNanos=227813} 14:53:36.010 [Test worker] INFO org.mongodb.driver.connection - Opened connection [connectionId{localValue:669, serverValue:601}] to localhost:27017 14:53:36.036 [Test worker] INFO org.mongodb.driver.connection - Closed connection [connectionId{localValue:669, serverValue:601}] to localhost:27017 because the pool has been closed.
I think the problem is that sometimes something else is getting into the profile collection