On 21 March 2016 at 04:32, Sean M. Collins <[email protected]> wrote:
> Rossella Sblendido wrote: > > 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 would rather remove all the single-node jobs. Nova has been moving to > multinode jobs for their gate (if I recall correctly my > conversation with Dan Smith) and we should be moving in this direction > too. We should test Neutron the way it is deployed in production. > > This was not true last time I checked. Switching to multinode jobs for the gate means that all projects in the integrated gate will have to use the miltinode configuration. > Also, who is really monitoring the periodic jobs? Truthfully? I know > there are some IPv6 jobs that are periodic and I'll be the first to > admit that I am not following them *at all*. > > So, my thinking is, unless it's running at the gate and inflicting pain > on people, it's not going to be a treated as a priority. Look at Linux > Bridge - serious race conditions that existed for years only > got fixed once I inflicted pain on all the Neutron devs by making it > voting and running on every patchset (sorry, not sorry). > > -- > Sean M. Collins > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
