Open Stack

Clark,

That is true. The check pipeline must pass in order to enter the gate pipeline. Here is the problem we are facing. A patch that was able to pass the check pipeline is blocked in gate pipeline, due to the instability of the test. The removal of unstable test from gate pipeline aims to unblock the patches that already passed the check.

An alternative is to remove the unstable test from check pipeline as well or mark it as non-voting test. If that is what the team prefers, I will adjust the review accordingly.

Best regards,
Honbgin

-----Original Message-----
From: Clark Boylan [mailto:cboylan at sapwetik.org] 
Sent: January-07-16 6:04 PM
To: openstack-dev at lists.openstack.org
Subject: Re: [openstack-dev] [magnum] Temporarily remove swarm func test from gate

On Thu, Jan 7, 2016, at 02:59 PM, Hongbin Lu wrote:
> Hi folks,
> 
> It looks the swarm func test is currently unstable, which negatively 
> impacts the patch submission workflow. I proposed to remove it from 
> Jenkins gate (but keep it in Jenkins check), until it becomes stable.
> Please find the details in the review
> (https://review.openstack.org/#/c/264998/) and let me know if you have 
> any concern.
> 
Removing it from gate but not from check doesn't necessarily help much because you can only enter the gate pipeline once the change has a +1 from Jenkins. Jenkins applies the +1 after check tests pass.

Clark

__________________________________________________________________________
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