Miloslav Trmač f6a3eddd2c Don't initialize the global RNG with GinkgoRandomSeed() in e2e tests ...

- It probably doesn't actually make a difference: in experiments,
  the github.com/containers/storage/pkg/stringid RNG initialization
  has been happening later
- This makes the RNG caller-controlled (which we don't benefit from),
  but also the same on all nodes of multi-process Ginkgo execution.
  So, if it works at all, it may make collisions of random ID values
  more likely, and our tests are not robust against that. So don't
  go out of our way to make collisions more likely.

Signed-off-by: Miloslav Trmač <mitr@redhat.com>

2022-01-03 12:31:47 +01:00

..

common_function_test.go

e2e tests: enable golint

2021-11-29 08:30:00 -07:00

matchers.go

a few more manual BeTrue cleanups

2021-11-30 10:13:16 -07:00

podmansession_test.go

bump go module to v3

2021-02-22 09:03:51 +01:00

podmantest_test.go

test: run --cgroups=split in new cgroup

2021-11-04 13:16:17 +01:00

utils_suite_test.go

bump go module to v3

2021-02-22 09:03:51 +01:00

utils.go

Don't initialize the global RNG with GinkgoRandomSeed() in e2e tests

2022-01-03 12:31:47 +01:00