Ok so here's the latest. We've switched scenario001 to non-voting[0]
for now until Bug 1731063[1] can be resolved. We should be OK to start
merging thing in master as the other current issues don't appear to be
affecting the gate significantly as it stands. We still need to
understand why we're hi
On Sat, Nov 11, 2017 at 10:47 PM, Alex Schultz wrote:
> Ok so here's the current status of things. I've gone through some of
> the pending patches and sent them to the gate over the weekend since
> the gate was empty (yay!). We've managed to land a bunch of patches.
> That being said for any pa
Ok so here's the current status of things. I've gone through some of
the pending patches and sent them to the gate over the weekend since
the gate was empty (yay!). We've managed to land a bunch of patches.
That being said for any patch for master with scenario jobs, please do
not recheck/approve
So we have some good news and some bad news. The good news is that
we've managed to get the gate queue[0] under control since we've held
off on pushing new things to the gate. The bad news is that we've
still got some random failures occurring during the deployment of
master. Since we're not see
Hey Folks
So we're at 24+ hours again in the gate[0] and the queue only
continues to grow. We currently have 6 ci/alert bugs[1]. Please do not
approve of recheck anything that isn't related to these bugs. I will
most likely need to go through the queue and abandon everything to
clear it up as we
