[FAB-14096] CouchDB container remains after unit-tests

Fixed bug where a single CouchDB container is left behind after the fabric unit-tests finish running Change-Id: I003521d13445a1289459c243bfbca4ab09f250ab Signed-off-by: Brett Logan <Brett.T.Logan@ibm.com>
hyperledger · Feb 19, 2019 · 027bb89 · 027bb89
1 parent b828f7f
commit 027bb89
Showing 1 changed file with 0 additions and 2 deletions.
diff --git a/core/ledger/kvledger/txmgmt/txmgr/lockbasedtxmgr/txmgr_test.go b/core/ledger/kvledger/txmgmt/txmgr/lockbasedtxmgr/txmgr_test.go
@@ -1083,8 +1083,6 @@ func producePvtdata(t *testing.T, txNum uint64, nsColls []string, keys []string,
 func TestRemoveStaleAndCommitPvtDataOfOldBlocks(t *testing.T) {
 	for _, testEnv := range testEnvs {
 		t.Logf("Running test for TestEnv = %s", testEnv.getName())
-		testLedgerID := "testvalidationandcommitofoldpvtdata"
-		testEnv.init(t, testLedgerID, nil)
 		testValidationAndCommitOfOldPvtData(t, testEnv)
 		testEnv.cleanup()
 	}