/*
Copyright IBM Corp. All Rights Reserved.

SPDX-License-Identifier: Apache-2.0
*/

package runner

import (
	"time"

	"github.com/hyperledger/fabric/integration/helpers"
)

const DefaultStartTimeout = 45 * time.Second

// DefaultNamer is the default naming function.
var DefaultNamer NameFunc = helpers.UniqueName

// A NameFunc is used to generate container names.
type NameFunc func() string

/*
Copyright IBM Corp. All Rights Reserved.

SPDX-License-Identifier: Apache-2.0
*/

package runner

import (
	"time"

	"github.com/hyperledger/fabric/integration/helpers"
)

const DefaultStartTimeout = 30 * time.Second

// DefaultNamer is the default naming function.
var DefaultNamer NameFunc = helpers.UniqueName

// A NameFunc is used to generate container names.
type NameFunc func() string

--- 
+++ 
@@ -12,7 +12,7 @@
 	"github.com/hyperledger/fabric/integration/helpers"
 )
 
-const DefaultStartTimeout = 30 * time.Second
+const DefaultStartTimeout = 45 * time.Second
 
 // DefaultNamer is the default naming function.
 var DefaultNamer NameFunc = helpers.UniqueName
Increase integration runner start timeout

Since moving to the official couchdb image, there
have been numerous unit test failures due to the
couchdb container not starting within the 30 second
start timeout. Increasing to 45 seconds seems to
be a sufficient amount of time.

FAB-15396 #done

Change-Id: I11e0ae84a39786d4c29f87aa0d3de2ec3f2615e9
Signed-off-by: Will Lahti <f19a2779710675aad3df5c81e4ecfde11707e3aa@us.ibm.com>
