Thank you for that information. I see that rechecks page referenced from the wiki now that you have mentioned it. I have learned something.
Carl Sent from my HTC ----- Reply message ----- From: "Davanum Srinivas" <[email protected]> To: "OpenStack Development Mailing List" <[email protected]> Subject: [openstack-dev] [Neutron] Gate breakage for multi-process API patch. Date: Mon, Sep 9, 2013 5:49 PM Carl, if you check the "rechecks" page - http://status.openstack.org/rechecks/ you will see 18 other reviews hitting the same bug reported at https://bugs.launchpad.net/tempest/+bug/1197476. So, in your review for https://review.openstack.org/#/c/37131/, add a comment "recheck bug 1197476" which will basically re-run the jenkins tests and update the rechecks page with your review number. See here for more info - https://wiki.openstack.org/wiki/GerritJenkinsGit#Test_Failures -- dims On Mon, Sep 9, 2013 at 6:40 PM, Baldwin, Carl (HPCS Neutron) <[email protected]<mailto:[email protected]>> wrote: Hi all, https://review.openstack.org/#/c/37131/ This review has been consistently marked as fail for the last three patch sets. I'm scratching my head over how the failure is related to the patch. Can anyone lend some insight? Is this a known failure that is not caused by my patch or is this failure actually due to my patch? The test breaking is "test_008_check_public_network_connectivity." I have run the patch with the new api_workers config option set to 0, 1, 2, and 5 and I've been able to create instances that have full network connectivity to my public network in each case. Thanks, Carl _______________________________________________ OpenStack-dev mailing list [email protected]<mailto:[email protected]> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Davanum Srinivas :: http://davanum.wordpress.com _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
