On existing Neutron patches, a comment of 'check experimental' will lead to the execution of the multi-node CI for DVR. As this graph shows:
http://graphite.openstack.org/render/?from=-10days&height=500&until=now&width=1200&bgcolor=ffffff&fgcolor=000000&yMax=100&yMin=0&target=color(alias(movingAverage(asPercent(stats.zuul.pipeline.check.job.check-tempest-dsvm-neutron-dvr.FAILURE,sum(stats.zuul.pipeline.check.job.check-tempest-dsvm-neutron-dvr.{SUCCESS,FAILURE})),%2736hours%27),%20%27check-tempest-dsvm-neutron-dvr%27),%27orange%27)&target=color(alias(movingAverage(asPercent(stats.zuul.pipeline.experimental.job.check-tempest-dsvm-neutron-multinode-full.FAILURE,sum(stats.zuul.pipeline.experimental.job.check-tempest-dsvm-neutron-multinode-full.{SUCCESS,FAILURE})),%2736hours%27),%20%27check-tempest-dsvm-neutron-multinode-full%27),%27blue%27)
The failure rate for the multi-node job is pretty lousy.
On existing Neutron patches, a comment of 'check experimental' will lead to the execution of the multi-node CI for DVR. As this graph shows:
http:// graphite. openstack. org/render/ ?from=- 10days& height= 500&until= now&width= 1200&bgcolor= ffffff& fgcolor= 000000& yMax=100& yMin=0& target= color(alias( movingAverage( asPercent( stats.zuul. pipeline. check.job. check-tempest- dsvm-neutron- dvr.FAILURE, sum(stats. zuul.pipeline. check.job. check-tempest- dsvm-neutron- dvr.{SUCCESS, FAILURE} )),%2736hours% 27),%20% 27check- tempest- dsvm-neutron- dvr%27) ,%27orange% 27)&target= color(alias( movingAverage( asPercent( stats.zuul. pipeline. experimental. job.check- tempest- dsvm-neutron- multinode- full.FAILURE, sum(stats. zuul.pipeline. experimental. job.check- tempest- dsvm-neutron- multinode- full.{SUCCESS, FAILURE} )),%2736hours% 27),%20% 27check- tempest- dsvm-neutron- multinode- full%27) ,%27blue% 27)
The failure rate for the multi-node job is pretty lousy.