[Cinder.glusterfs.ci] [Third-party-announce] Fwd: IBM DB2 CI spam alot

[Anita Kuno]

On 06/11/2015 10:14 AM, Sean Dague wrote:
> On 06/11/2015 10:02 AM, Anita Kuno wrote:
>> On 06/11/2015 05:09 AM, yan fengxi wrote:
>>> Hi, everyone. The annoying problem is now resolved. But I found the DB2 CI
>>> account was already disabled.
>>> We need to get it enabled, so that we could test if our solution works, and
>>> we will not publish any results to community until then.
>>>
>>> @*Anita Kuno, would you please help on this?*
>>
>> If Sean agrees this is satisfactory, then yes, I can support your system
>> being re-enabled.
> 
> Yes, sounds fine.

Thank you, Sean.

Yan Fengxi, your gerrit account is re-enabled. I suggest following up
with Sean on irc (sdague) after you begin commenting again to ensure
what you are posting is inline with expectations.

Thank you,
Anita.

> 
>>
>> Thank you,
>> Anita.
>>>
>>>
>>> ---------- Forwarded message ----------
>>> From: yan fengxi <goodyfx at gmail.com>
>>> Date: Thu, Jun 11, 2015 at 2:01 PM
>>> Subject: IBM DB2 CI spam alot
>>> To: sean at dague.net
>>> Cc: openstack-infra at lists.openstack.org, yanfengxi at cn.ibm.com,
>>> goodyfx at gmail.com
>>>
>>>
>>> Hi, Sean, I am the DB2 CI maintainer "yanfengxi". Thanks for reminding us
>>> this problem. It is indeed annoying to see merge failures.
>>> Now our team is trying to resolv this problem, by stopping to publish this
>>> kind of failures. Before it's resolved, our DB2 CI will not publish result
>>> to community.
>>>
>>> Actually, not long ago, we met merge failure errors. We configured our zuul
>>> to stop publishing "Merge failure" errors on specific patch. But we were
>>> not aware that patches that depends on the failed patch will also publish
>>> merge failures.
>>>
>>> Cheers
>>> Feng Xi Yan(yanfengxi at cn.ibm.com)
>>>
>>> On Thu, Jun 11, 2015 at 5:26 AM, Sean Dague <sean at dague.net
>>> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra>>
>>> wrote:
>>>> * The IBM DB2 CI seems to be running a Zuul, and seems to be reporting
>>> *>* back on merge conflicts a lot in completely unhelpful ways -
>>> *>* https://review.openstack.org/#/c/188148/
>>> <https://review.openstack.org/#/c/188148/>
>>> *>>* It seems like no 3rd party CI should be sending merge conflict messages
>>> *>* to gerrit. This is my formal complaint on that front, and I'd like the
>>> *>* CI system turned off if it's not fixed in the near term.
>>> *>>*         -Sean
>>> *>>* --
>>> *>* Sean Dague
>>> *>* http://dague.net <http://dague.net/>
>>> *>>* _______________________________________________
>>> *>* OpenStack-Infra mailing list
>>> *>* OpenStack-Infra at lists.openstack.org
>>> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra>
>>> *>* http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra>*
>>>
>>
> 
> 


_______________________________________________
Third-party-announce mailing list
Third-party-announce at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce