device: run fewer iterations in TestUpDown

The high iteration count was useful when TestUpDown
was the nexus of new bugs to investigate.

Now that it has stabilized, that's less valuable.
And it slows down running the tests and crowds out other tests.

Signed-off-by: Josh Bleecher Snyder <josh@tailscale.com>

diff --git a/device/device_test.go b/device/device_test.go
index 8f16207c2341eff3c8baf589e9ad312d403d64da..ce1ba9ba35831248551ee440eb2e7e8eaa085707 100644 (file)
--- a/device/device_test.go
+++ b/device/device_test.go
@@ -196,8 +196,8 @@ func TestTwoDevicePing(t *testing.T) {
 
 func TestUpDown(t *testing.T) {
        goroutineLeakCheck(t)
-       const itrials = 200
-       const otrials = 10
+       const itrials = 20
+       const otrials = 1
 
        for n := 0; n < otrials; n++ {
                pair := genTestPair(t)