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>
This commit is contained in:
parent
d117d42ae7
commit
465261310b
@ -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)
|
||||
|
Loading…
Reference in New Issue
Block a user