> Looks like the CI is broken because this change is in merge conflict: > > https://review.opendev.org/#/c/506686/ > > Does anyone plan on working on that? It's had a -1 on it since August of > 2018. Is that change really needed for the CI to work? This work was done in [1], so I abandoned the above change. Of course, that won't help the CI to pass, since it appears to be hardcoding that patch number somewhere. Anyone know where the setup lives for this? (Or better yet, who owns it?) efried [1] https://review.opendev.org/#/c/611974/