On 2014-02-27 09:23, Daniel P. Berrange wrote:
On Thu, Feb 27, 2014 at 08:38:22AM -0500, Sean Dague wrote:
This patch is coming through the gate this morning -
https://review.openstack.org/#/c/71996/
The point being to actually make devstack stop when it hits an error,
instead of only once these compound to the point where there is no
moving forward and some service call fails. This should *dramatically*
improve the experience of figuring out a failure in the gate, because
where it fails should be the issue. (It also made us figure out some
wonkiness with stdout buffering, that was making debug difficult).
This works on all the content that devstack gates against. However,
there are a ton of other paths in devstack, including vendor plugins,
which I'm sure aren't clean enough to run under -o errexit. So if all
of
a sudden things start failing, this may be why. Fortunately you'll be
pointed at the exact point of the fail.
This is awesome!
+1! Thanks Sean and everyone else who was involved with this.
This should help reduce the number of "devstack failed, what went
wrong?" questions since the actual failure will be right there, as
opposed to buried a thousand lines of output up. :-)
-Ben
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
