[openstack-dev] [OpenStack-Dev] [third-party-ci] Clarifications on the goal and skipping tests
dougwig at parksidesoftware.com
Mon Mar 30 22:06:27 UTC 2015
A few reasons, I’m sure there are others:
- Broken tests that hardcode something about the ref implementation. The test needs to be fixed, of course, but in the meantime, a constantly failing CI is worthless (hello, lbaas scenario test.)
- Test relies on some “optional” feature, like overlapping IP subnets that the backend doesn’t support. I’d argue it’s another case of broken tests if they require an optional feature, but it still needs skipping in the meantime.
- Some new feature added to an interface, in the presence of shims/decomposed drivers/plugins (e.g. adding TLS termination support to lbaas.) Those implementations will lag the feature commit, by definition.
> On Mar 30, 2015, at 2:54 PM, John Griffith <john.griffith8 at gmail.com> wrote:
> This may have already been raised/discussed, but I'm kinda confused so thought I'd ask on the ML here. The whole point of third party CI as I recall was to run the same tests that we run in the official Gate against third party drivers. To me that would imply that a CI system/device that marks itself as "GOOD" doesn't do things like add skips locally that aren't in the tempest code already?
> In other words, seems like cheating to say "My CI passes and all is good, except for the tests that don't work which I skip... but pay no attention to those please".
> Did I miss something, isn't the whole point of Third Party CI to demonstrate that a third parties backend is tested and functions to the same degree that the reference implementations do? So the goal (using Cinder for example) was to be able to say that any API call that works on the LVM reference driver will work on the drivers listed in driverlog; and that we know this because they run the same Tempest API tests?
> Don't get me wrong, certainly not saying there's malice or things should be marked as no good... but if the practice is to skip what you can't do then maybe that should be documented in the driverlog submission, as opposed to just stating "Yeah, we run CI successfully".
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev