[Cinder.glusterfs.ci] [Third-party-announce] posting success after logging failure: Intel networking-odl CI

[Anita Kuno]

On 02/12/2016 06:06 AM, Ressi, Federico wrote:
> Hi Anita,
> 
> I have found the cause of the problem. There is bug here erasing value returned by test:
> 
> https://github.com/FedericoRessi/devstack-ws/blob/0f5b2197c128d12ba67792b1bfb9b5e0e3679223/Makefile#L172-L173
> 
> I am fixing it. There should be many other builds affected by this issue from the same CI.
> 
> Thanks for reporting

Well it was less reporting and more drawing attention to the fact that
logging failure and then posting success is not being truthful with the
community.

We expect honest reporting from CI systems. I look forward to it from
your system.

Thank you,
Anita.

> 
> Best regards
> Federico
> 
> On 10 Feb 2016, at 18:48, Anita Kuno <anteaya at anteaya.info<mailto:anteaya at anteaya.info>> wrote:
> 
> On 02/10/2016 12:41 PM, Ressi, Federico wrote:
> Hi,
> 
> I have to investigate it because I expected a failure as well on that case (upstream connection failed). It is a bug, not a wanted behaviour. The CI has been silenced until the problem is not solved. What I suppose is that there have been two reports (one success and one failed): successful execution overwrited the failure.
> 
> Federico
> 
> Yes, you have to investigate it. I'm glad to hear this was not intended
> behaviour.
> 
> Please post the full notes of your investigation and findings as well as
> your solution to address this so that other third party ci operators can
> learn and ensure they don't display the same behaviour.
> 
> Thank you,
> Anita.
> 
> 
> On 10 Feb 2016, at 16:38, Anita Kuno <anteaya at anteaya.info<mailto:anteaya at anteaya.info>> wrote:
> 
> Replying again to keep this public, I wrongly assumed you had addressed
> the list as well.
> 
> Anita.
> 
> On 02/10/2016 10:00 AM, Anita Kuno wrote:
> On 02/10/2016 04:29 AM, Ressi, Federico wrote:
> Hello,
> 
> What failed on this case was network connection with upstream. I have to investigate better on this, I don’t happen often. I would have expected a failure in any way. Thanks for reporting. I am going to also update the wiki. Sorry for the confusion.
> 
> In the logs folder there are more details.
> 
> Federico
> 
> I'm not asking you what failed.
> 
> I'm pointing out that a failure is being reported as success. This is my
> area of concern.
> 
> Please address why a failure is being reported as success.
> 
> Thank you,
> Anita.
> 
> 
> On 10 Feb 2016, at 08:33, Hejral, VaclavX <vaclavx.hejral at intel.com<mailto:vaclavx.hejral at intel.com>> wrote:
> 
> Hi Federico,
> 
> I received this and I am forwarding to you.
> 
> Vaclav
> 
> -----Original Message-----
> From: Anita Kuno [mailto:anteaya at anteaya.info]
> Sent: Wednesday, February 10, 2016 02:11
> To: Announcements for Third Party CI Operators. <third-party-announce at lists.openstack.org<mailto:third-party-announce at lists.openstack.org>>
> Subject: [Third-party-announce] posting success after logging failure: Intel networking-odl CI
> 
> On this patch: https://review.openstack.org/#/c/278151/1 Intel networking-odl CI posted SUCCESS
> 
> while the attached logs:
> http://intel-openstack-ci-logs.ovh/networking-odl-vhostuser-ci/refs/changes/51/278151/1/2016-02-09_23:56:52/console.html
> exited with Status: FAILED
> 
> Could someone associated with Intel networking-odl CI help me understand why?
> 
> I would cc the operators of this system if I knew who they were, but this system is not listed on the wikipage:
> https://wiki.openstack.org/wiki/ThirdPartySystems
> 
> Please update this wikipage with your system as required in Third Party requirements and help me understand why your system is posting SUCCESS on Status: FAILED.
> 
> Thank you,
> Anita.
> 
> _______________________________________________
> Third-party-announce mailing list
> Third-party-announce at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce
> Please attend the third party meetings: http://eavesdrop.openstack.org/#Third_Party_Meeting
> 
> --------------------------------------------------------------
> Intel Research and Development Ireland Limited
> Registered in Ireland
> Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
> Registered Number: 308263
> 
> 
> This e-mail and any attachments may contain confidential material for the sole
> use of the intended recipient(s). Any review or distribution by others is
> strictly prohibited. If you are not the intended recipient, please contact the
> sender and delete all copies.
> 
> 
> 
> 
> --------------------------------------------------------------
> Intel Research and Development Ireland Limited
> Registered in Ireland
> Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
> Registered Number: 308263
> 
> 
> This e-mail and any attachments may contain confidential material for the sole
> use of the intended recipient(s). Any review or distribution by others is
> strictly prohibited. If you are not the intended recipient, please contact the
> sender and delete all copies.
> 
> 
> 
> --------------------------------------------------------------
> Intel Research and Development Ireland Limited
> Registered in Ireland
> Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
> Registered Number: 308263
> 
> 
> This e-mail and any attachments may contain confidential material for the sole
> use of the intended recipient(s). Any review or distribution by others is
> strictly prohibited. If you are not the intended recipient, please contact the
> sender and delete all copies.
> 


_______________________________________________
Third-party-announce mailing list
Third-party-announce at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce
Please attend the third party meetings: http://eavesdrop.openstack.org/#Third_Party_Meeting