1dedea2fb8
Multiple daemons starting/running concurrently can collide with each
other when editing iptables rules. Most integration tests which opt into
parallelism and start daemons work around this problem by starting the
daemon with the --iptables=false option. However, some of the tests
neglect to pass the option when starting or restarting the daemon,
resulting in those tests being flaky.
Audit the integration tests which call t.Parallel() and (*Daemon).Stop()
and add --iptables=false arguments where needed.
Signed-off-by: Cory Snider <csnider@mirantis.com>
(cherry picked from commit
|
||
|---|---|---|
| .. | ||
| commit_test.go | ||
| import_test.go | ||
| list_test.go | ||
| main_test.go | ||
| pull_test.go | ||
| remove_test.go | ||
| remove_unix_test.go | ||
| tag_test.go | ||