open-nomad/nomad/volumewatcher
Tim Gross 81ae581da6
test: remove flaky test from volumewatcher (#8189)
The volumewatcher restores itself on notification, but detecting this is racy
because it may reap any claim (or find there are no claims to reap) and
shutdown before we can test whether it's running. This appears to have become
flaky with a new version of golang. The other cases in this test case
sufficiently exercise the start/stop behavior of the volumewatcher, so remove
the flaky section.
2020-06-17 15:41:51 -04:00
..
batcher.go refactor: context is first parameter 2020-05-26 10:18:09 -04:00
batcher_test.go refactor: context is first parameter 2020-05-26 10:18:09 -04:00
interfaces.go csi: move volume claim release into volumewatcher (#7794) 2020-04-30 09:13:00 -04:00
interfaces_test.go csi: move volume claim release into volumewatcher (#7794) 2020-04-30 09:13:00 -04:00
volume_watcher.go csi: support Secrets parameter in CSI RPCs (#7923) 2020-05-11 17:12:51 -04:00
volume_watcher_test.go csi: move volume claim release into volumewatcher (#7794) 2020-04-30 09:13:00 -04:00
volumes_watcher.go {volume|deployment}watcher: check for nil batcher 2020-05-26 14:54:27 -04:00
volumes_watcher_test.go test: remove flaky test from volumewatcher (#8189) 2020-06-17 15:41:51 -04:00