Closed JeffreyDevloo closed 7 years ago
Searching the reason behind the error revealed some api flaw as well. Updating all of it at once
Fixed by https://github.com/openvstorage/integrationtests/pull/500, packed in openvstorage-test-3.1.1-dev.1491236165.9103ee2
Problem description
Adjust setup logic. Our test is giving of a wrong result.
In reference to https://github.com/openvstorage/framework/issues/1495
What went wrong
The timeout specified in the test is 60s. This can be justified as to we expect it to complete in that time. The setup code however will catch the runtimeerror thrown by the api and check if the storagedriver is created, which it most likely is at that point.