Skip to content

Commit 1fda731

Browse files
cpugopherbot
authored andcommitted
acme: increase pebble test waitForServer attempts
In CI it seems that occasionally we can't connect to the test servers within 10 tries, and the test flakes. Let's give the process more attempts. Updates golang/go#74437 Change-Id: I74d6cea83468a3a572ec4b52ff7314c778c664cf Cq-Include-Trybots: luci.golang.try:x_crypto-gotip-linux-amd64-longtest Reviewed-on: https://go-review.googlesource.com/c/crypto/+/692075 Auto-Submit: Daniel McCarney <daniel@binaryparadox.net> Reviewed-by: Roland Shoemaker <roland@golang.org> Reviewed-by: Mark Freeman <mark@golang.org> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
1 parent 1b4c3d2 commit 1fda731

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

acme/pebble_test.go

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -692,14 +692,14 @@ func startPebbleEnvironment(t *testing.T, config *environmentConfig) environment
692692
func waitForServer(t *testing.T, addr string) {
693693
t.Helper()
694694

695-
for i := 0; i < 10; i++ {
695+
for i := 0; i < 20; i++ {
696696
if conn, err := net.Dial("tcp", addr); err == nil {
697697
conn.Close()
698698
return
699699
}
700700
time.Sleep(time.Duration(i*100) * time.Millisecond)
701701
}
702-
t.Fatalf("failed to connect to %q after 10 tries", addr)
702+
t.Fatalf("failed to connect to %q after 20 tries", addr)
703703
}
704704

705705
// fetchModule fetches the module at the given version and returns the directory

0 commit comments

Comments
 (0)