Chris Evich 437d9d2cde Move noCache logic lower in stack ... One or more tests are not taking advantage of the local image cache. This has been observed to cause a testing flake in at least one `--sigproxy` test which uses `PodmanTestIntegration.PodmanPID()`. It has a rather short timeout of 15-seconds, which isn't always enough time to pull down a remote image. Fix this by reloacing the `noCache` logic from `PodmanTest.PodmanAsUserBase()` down the stack into `PodmanTestIntegration.makeOptions()`. This also eliminates the need to also check if a remote-client is being used - since it uses a different function. Also reverse the parameter order in `PodmanTest.PodmanBase` so that everywhere is consistently `noEvents` then `noCache`. Signed-off-by: Chris Evich <cevich@redhat.com>		2019-09-26 10:56:24 -04:00
..
common_function_test.go	Change all 'can not' to 'cannot' for proper usage	2018-12-21 10:27:54 -05:00
podmansession_test.go	Separate common used test functions and structs to test/utils	2018-11-16 10:49:00 +08:00
podmantest_test.go	Do not use an events backend when restoring images	2019-07-31 17:28:42 -04:00
utils.go	Move noCache logic lower in stack	2019-09-26 10:56:24 -04:00
utils_suite_test.go	Move noCache logic lower in stack	2019-09-26 10:56:24 -04:00