Re: [openstack-dev] [cinder] 3rd Party CI failures ignored, caused driver to break

2015-03-10 Thread Erlon Cruz
Agreed, CI systems are not reliable. Most of failures are related to mis-configuration or devstack problems, not driver problems itself. What happen then, is that people just don't care if there's a red FAILURE in the CIs results. A 4) option would be to rate CIs according to their trustfulness

Re: [openstack-dev] [cinder] 3rd Party CI failures ignored, caused driver to break

2015-02-26 Thread John Griffith
On Thu, Feb 26, 2015 at 1:10 PM, Walter A. Boring IV walter.bor...@hp.com wrote: Hey folks, Today we found out that a patch[1] that was made against our lefthand driver caused the driver to fail. The 3rd party CI that we have setup to test our driver (hp_lefthand_rest_proxy.py) caught

[openstack-dev] [cinder] 3rd Party CI failures ignored, caused driver to break

2015-02-26 Thread Walter A. Boring IV
Hey folks, Today we found out that a patch[1] that was made against our lefthand driver caused the driver to fail. The 3rd party CI that we have setup to test our driver (hp_lefthand_rest_proxy.py) caught the CI failure and reported it correctly[2]. The patch that broke the driver was