From 465261310b55898c3f67809bd56d58442bca4554 Mon Sep 17 00:00:00 2001 From: Josh Bleecher Snyder Date: Tue, 9 Feb 2021 08:20:11 -0800 Subject: 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 --- device/device_test.go | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'device') diff --git a/device/device_test.go b/device/device_test.go index 8f16207..ce1ba9b 100644 --- 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) -- cgit v1.2.3