Added project prefix in the subject and loop in Masayuki and Ghanshyam who know the background as well. Thanks.
Jianghua From: Jianghua Wang Sent: Tuesday, June 14, 2016 12:46 PM To: OpenStack Development Mailing List (not for usage questions) Cc: Jianghua Wang Subject: Discussion on to enable "Citrix XenServer CI" to vote openstack/tempest Hi all, Recently the "Citrix XenServer CI" was broken due to a bad commit[1] to openstack/tempest. As the commit was merged on Friday which is vacation at here, it had been in failure for more than three days before we noticed and fixed[2] this problem. As this CI votes for openstack/nova, it had been keeping to vote -1 until disabled voting. So I suggest we also enable this XenServer CI voting on tempest change to avoid similar cases in the future. We see in this case, the tempest commit didn't consider the different case for type-1 hypervisors, so it broke XenServer test. Actually "Citrix XenServer CI" verified that patch set with failure result but which got ignored due to no voting. So let's enable the voting to make life easier:) Currently we have this CI voting for openstack/nova. Per the history experience, it has been a stable CI(more stable than the Jenkins check) normally if there is no bad commit breaking it. Thanks for any comments. [1] https://review.openstack.org/#/c/316672 [2] https://review.openstack.org/#/c/328836/ Regards, Jianghua
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
