On 24/04/2019 14.50, Daniel P. Berrangé wrote: [...] > For automated CI, I think we should set clear desired featureset upfront > based on what we know we are supposde to have available and not silently > skip tests
If someone really cares about running an certain iotest that depends on an optional feature in a CI system (so far there apparently was not much interest yet - see e.g. .travis.yml), you can also manually list the tests that you care about in the corresponding yml file. I did so in the .gitlab-ci.yml already for a couple of tests. Feel free to add some more tests there after making sure that the corresponding features are enabled in the build process before. Thomas
