Open Stack

Jichen-

	That patch is not ever intended to merge; hope that was clear from the
start :) It was just a proving ground to demonstrate which tests still
pass when there's effectively no compute driver in play.

	We haven't taken any action on this from our end, though we have done a
little brainstorming about how we would tool our CI to skip those tests
most (but not all) of the time. Happy to share our experiences with you
if/as we move forward with that.

	Regarding the tempest-level automation, I certainly had z in mind when
I was thinking about it. If you have the time and inclination to help
look into it, that would be most welcome.

Thanks,
efried

On 09/06/2018 12:33 AM, Chen CH Ji wrote:
> I see the patch is still ongoing status and do you have a follow up
> plan/discussion for that? we are maintaining 2 CIs (z/VM and KVM on z)
> so skip non-compute related cases will be a good for 3rd part CI .. thanks
> 
> Best Regards!
> 
> Kevin (Chen) Ji 纪 晨
> 
> Engineer, zVM Development, CSTL
> Notes: Chen CH Ji/China/IBM at IBMCN Internet: jichenjc at cn.ibm.com
> Phone: +86-10-82451493
> Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian
> District, Beijing 100193, PRC
> 
> Inactive hide details for Eric Fried ---09/04/2018 09:35:09 PM---Folks-
> The other day, I posted an experimental patch [1] withEric Fried
> ---09/04/2018 09:35:09 PM---Folks- The other day, I posted an
> experimental patch [1] with an effectively
> 
> From: Eric Fried <openstack at fried.cc>
> To: "OpenStack Development Mailing List (not for usage questions)"
> <openstack-dev at lists.openstack.org>
> Date: 09/04/2018 09:35 PM
> Subject: [openstack-dev] [tempest][CI][nova compute] Skipping
> non-compute-driver tests
> 
> ------------------------------------------------------------------------
> 
> 
> 
> Folks-
> 
> The other day, I posted an experimental patch [1] with an effectively
> empty ComputeDriver (just enough to make n-cpu actually start) to see
> how much of our CI would pass. The theory being that any tests that
> still pass are tests that don't touch our compute driver, and are
> therefore not useful to run in our CI environment. Because anything that
> doesn't touch our code should already be well covered by generic
> dsvm-tempest CIs. The results [2] show that 707 tests still pass.
> 
> So I'm wondering whether there might be a way to mark tests as being
> "compute driver-specific" such that we could switch off all the other
> ones [3] via a one-line conf setting. Because surely this has potential
> to save a lot of CI resource not just for us but for other driver
> vendors, in tree and out.
> 
> Thanks,
> efried
> 
> [1] https://review.openstack.org/#/c/599066/
> [2]
> http://184.172.12.213/66/599066/5/check/nova-powervm-out-of-tree-pvm/a1b42d5/powervm_os_ci.html.gz
> [3] I get that there's still value in running all those tests. But it
> could be done like once every 10 or 50 or 100 runs instead of every time.
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> 
> 
> 
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>