Cory Snider cdcb7c28c5 integration: disable iptables in parallel tests ...

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>

2023-07-05 13:49:53 -04:00

..

commit_test.go

Using test names instead of hardcoded ones in integration/image directory

2020-05-18 16:37:09 +01:00

import_test.go

integration: disable iptables in parallel tests

2023-07-05 13:49:53 -04:00

inspect_test.go

testutil/environment: Add GetTestDanglingImageId

2023-06-30 18:18:45 +02:00

list_test.go

List images with multiple since/before filters

2022-12-08 16:36:57 -05:00

main_test.go

testutil: make testing packages public

2019-09-11 07:47:23 -05:00

prune_test.go

c8d/prune: Exclude dangling tag of the images used by containers

2023-06-30 18:18:56 +02:00

pull_test.go

testutil/environment: remove Execution.OSType field

2023-06-26 11:18:09 +02:00

remove_test.go

Windows: Enable more integration tests

2020-09-20 22:09:27 +03:00

remove_unix_test.go

remove pre-go1.17 build-tags

2023-05-19 20:38:51 +02:00

save_test.go

testutil/environment: remove Execution.OSType field

2023-06-26 11:18:09 +02:00

tag_test.go

Windows: Enable more integration tests

2020-09-20 22:09:27 +03:00