[openstack-dev] [trove] Can we move some non-voting broken jobs to the experimental queue?
amrith.kumar at gmail.com
Thu Aug 3 03:41:25 UTC 2017
Matt, we're trying our best to and the reason they were (recently) moved
back to NON-experimental is that in moving them to experimental, no one
Yes, I am trying to get them to voting and like everything else in Trove,
we could use some help.
Yes, I realize that there are no elements, and yes, they are failing.
I would recommend against moving them to the experimental queue. But, if
someone else wants to propose the change, I'll leave it up to infra to
decide; that's not my decision.
On Wed, Aug 2, 2017 at 10:27 AM, Matt Riedemann <mriedemos at gmail.com> wrote:
> I don't dabble in Trove-land often but today I pushed a change and was
> watching it in zuul, and noticed that the change runs 26 jobs in the check
> queue. Several of those (cassandra, couch, mongo, percona) all failed
> nearly immediately with something in the diskimage builder, like this:
> diskimage_builder.element_dependencies.MissingElementException: Element
> 'ubuntu-xenial-cassandra' not found
> Is anyone maintaining these jobs? If not, they should be moved to the
> experimental queue so they can be run on demand, not in the check queue for
> every patch set proposed to Trove. These are also single and multi-node
> jobs, so they are needlessly eating up node pool resources.
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev