Re: [openstack-dev] [trove] Can we move some non-voting broken jobs to the experimental queue?

[Amrith Kumar]

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
monitored them.

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.​

-amrith



On Wed, Aug 2, 2017 at 10:27 AM, Matt Riedemann  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:
>
> http://logs.openstack.org/42/490042/1/check/gate-trove-scena
> rio-dsvm-cassandra-single-ubuntu-xenial-nv/d38a8c1/logs/
> devstack-gate-post_test_hook.txt.gz#_2017-08-02_14_58_16_953
>
> 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.
>
> --
>
> Thanks,
>
> Matt
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [trove] Can we move some non-voting broken jobs to the experimental queue?

[Matt Riedemann]

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:


http://logs.openstack.org/42/490042/1/check/gate-trove-scenario-dsvm-cassandra-single-ubuntu-xenial-nv/d38a8c1/logs/devstack-gate-post_test_hook.txt.gz#_2017-08-02_14_58_16_953

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.


--

Thanks,

Matt

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev