<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi, Sean,<br></blockquote><div>I've tested the DB2 CI on your patch <a href="https://review.openstack.org/#/c/188148/">https://review.openstack.org/#/c/188148/</a>, and it worked fine, it did not publish that annoying merge failures any more. </div><div>As you are not online in irc, I will take a risk to enable publishing of DB2 CI. If there are problems, please reach me any time via mailing-list or my private email: <a href="mailto:yanfengxi@cn.ibm.com">yanfengxi@cn.ibm.com</a>.</div><div><br></div><div>@Anita Kuno, thanks for you support on this :)</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Thu, 11 Jun 2015 10:20:29 -0400<br>
From: Anita Kuno <<a href="mailto:anteaya@anteaya.info">anteaya@anteaya.info</a>><br>
To: Sean Dague <<a href="mailto:sean@dague.net">sean@dague.net</a>>, yan fengxi <<a href="mailto:goodyfx@gmail.com">goodyfx@gmail.com</a>>,<br>
<a href="mailto:openstack-infra@lists.openstack.org">openstack-infra@lists.openstack.org</a>, "Announcements for Third Party<br>
CI Operators." <<a href="mailto:third-party-announce@lists.openstack.org">third-party-announce@lists.openstack.org</a>><br>
Subject: Re: [OpenStack-Infra] Fwd: IBM DB2 CI spam alot<br>
Message-ID: <<a href="mailto:5579992D.60006@anteaya.info">5579992D.60006@anteaya.info</a>><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
On 06/11/2015 10:14 AM, Sean Dague wrote:<br>
> On 06/11/2015 10:02 AM, Anita Kuno wrote:<br>
>> On 06/11/2015 05:09 AM, yan fengxi wrote:<br>
>>> Hi, everyone. The annoying problem is now resolved. But I found the DB2 CI<br>
>>> account was already disabled.<br>
>>> We need to get it enabled, so that we could test if our solution works, and<br>
>>> we will not publish any results to community until then.<br>
>>><br>
>>> @*Anita Kuno, would you please help on this?*<br>
>><br>
>> If Sean agrees this is satisfactory, then yes, I can support your system<br>
>> being re-enabled.<br>
><br>
> Yes, sounds fine.<br>
<br>
Thank you, Sean.<br>
<br>
Yan Fengxi, your gerrit account is re-enabled. I suggest following up<br>
with Sean on irc (sdague) after you begin commenting again to ensure<br>
what you are posting is inline with expectations.<br>
<br>
Thank you,<br>
Anita.<br>
<br>
><br>
>><br>
>> Thank you,<br>
>> Anita.<br>
>>><br>
>>><br>
>>> ---------- Forwarded message ----------<br>
>>> From: yan fengxi <<a href="mailto:goodyfx@gmail.com">goodyfx@gmail.com</a>><br>
>>> Date: Thu, Jun 11, 2015 at 2:01 PM<br>
>>> Subject: IBM DB2 CI spam alot<br>
>>> To: <a href="mailto:sean@dague.net">sean@dague.net</a><br>
>>> Cc: <a href="mailto:openstack-infra@lists.openstack.org">openstack-infra@lists.openstack.org</a>, <a href="mailto:yanfengxi@cn.ibm.com">yanfengxi@cn.ibm.com</a>,<br>
>>> <a href="mailto:goodyfx@gmail.com">goodyfx@gmail.com</a><br>
>>><br>
>>><br>
>>> Hi, Sean, I am the DB2 CI maintainer "yanfengxi". Thanks for reminding us<br>
>>> this problem. It is indeed annoying to see merge failures.<br>
>>> Now our team is trying to resolv this problem, by stopping to publish this<br>
>>> kind of failures. Before it's resolved, our DB2 CI will not publish result<br>
>>> to community.<br>
>>><br>
>>> Actually, not long ago, we met merge failure errors. We configured our zuul<br>
>>> to stop publishing "Merge failure" errors on specific patch. But we were<br>
>>> not aware that patches that depends on the failed patch will also publish<br>
>>> merge failures.<br>
>>><br>
>>> Cheers<br>
>>> Feng Xi Yan(<a href="mailto:yanfengxi@cn.ibm.com">yanfengxi@cn.ibm.com</a>)<br>
>>><br>
>>> On Thu, Jun 11, 2015 at 5:26 AM, Sean Dague <sean at <a href="http://dague.net" target="_blank">dague.net</a><br>
>>> <<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra</a>>><br>
>>> wrote:<br>
>>>> * The IBM DB2 CI seems to be running a Zuul, and seems to be reporting<br>
>>> *>* back on merge conflicts a lot in completely unhelpful ways -<br>
>>> *>* <a href="https://review.openstack.org/#/c/188148/" target="_blank">https://review.openstack.org/#/c/188148/</a><br>
>>> <<a href="https://review.openstack.org/#/c/188148/" target="_blank">https://review.openstack.org/#/c/188148/</a>><br>
>>> *>>* It seems like no 3rd party CI should be sending merge conflict messages<br>
>>> *>* to gerrit. This is my formal complaint on that front, and I'd like the<br>
>>> *>* CI system turned off if it's not fixed in the near term.<br>
>>> *>>* -Sean<br>
>>> *>>* --<br>
>>> *>* Sean Dague<br>
>>> *>* <a href="http://dague.net" target="_blank">http://dague.net</a> <<a href="http://dague.net/" target="_blank">http://dague.net/</a>><br>
>>> *>>* _______________________________________________<br>
>>> *>* OpenStack-Infra mailing list<br>
>>> *>* OpenStack-Infra at <a href="http://lists.openstack.org" target="_blank">lists.openstack.org</a><br>
>>> <<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra</a>><br>
>>> *>* <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra</a><br>
>>> <<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra</a>>*<br>
>>><br>
>><br>
><br>
><br></blockquote></div></div></div>