[openstack-dev] [neutron] CI jobs take pretty long, can we improve that?

Rossella Sblendido rsblendido at suse.com
Mon Mar 21 11:15:30 UTC 2016

Hello all,

the tests that we run on the gate for Neutron take pretty long (longer
than one hour). I think we can improve that and make better use of the
Here are some ideas that came up when Ihar and I discussed this topic
during the sprint in Brno:

1) We have few jobs that are non-voting. I think it's OK to have
non-voting jobs for a limited amount of time, while we try to make them
stable but this shouldn't be too long, otherwise we waste time running
those tests without even using the results. If a job is still not-voting
after 3 months (or 4 or 6, we can find a good time interval) the job
should be removed. My hope is that this threat will make us find some
time to actually fix the job and make it vote :)

2) multi-node jobs run for every patch set. Is that really what we want?
They take pretty long. We could move them to a periodic job. I know we
can easily forget about periodic jobs, to avoid that we could run them
in the gate queue too. If a patch can't merge because of a failure we
will fix the issue. To trigger them for a specific patch that might
affect multi-node we can run the experimental jobs.



More information about the OpenStack-dev mailing list