[openstack-dev] [Neutron][LBaaS] Jenkins CI failure for patch: https://review.openstack.org/180019
Hello,
I am seeing odd behavior with Jenkins CI for the patch:
https://review.openstack.org/180019
A quick background:
1. I could see all the tests passing on my virtual box and have attached
the logs for your ready reference.
2. Whereas in Jenkins, I could see the different behavior which is not
reproducible on my virtual box. I have tried the following to make it
succeed.
(a) 'recheck' comment - Jenkins reported unhappy.
(b) restacked my devstack instance on my vm and run 'tox -e tempest', it
succeeds on virtual box, but not for Jenkins.
Not sure of the exact problem though, but would like to have community help
on the same.
Thanks!
Madhu
devstack@ubuntu:/opt/stack/neutron-lbaas/neutron_lbaas/tests/tempest/v2/scenario$
git commit --amend
[review/madhusudhan_kandadai/pools_admin_ddt_tests acba386] Tempest tests using
testscenarios for create/update pool
Author: Ubuntu madhusudhan.openst...@gmail.com
1 file changed, 169 insertions(+)
create mode 100644
neutron_lbaas/tests/tempest/v2/scenario/test_pools_admin_state.py
devstack@ubuntu:/opt/stack/neutron-lbaas/neutron_lbaas/tests/tempest/v2/scenario$
devstack@ubuntu:/opt/stack/neutron-lbaas/neutron_lbaas/tests/tempest/v2/scenario$
devstack@ubuntu:/opt/stack/neutron-lbaas/neutron_lbaas/tests/tempest/v2/scenario$
devstack@ubuntu:/opt/stack/neutron-lbaas/neutron_lbaas/tests/tempest/v2/scenario$
git review
remote: Resolving deltas: 100% (5/5)
remote: Processing changes: updated: 1, refs: 1, done
remote:
remote: Updated Changes:
remote: https://review.openstack.org/180019 Tempest tests using testscenarios
for create/update pool
remote:
To
ssh://madhusudhan-kanda...@review.openstack.org:29418/openstack/neutron-lbaas.git
* [new branch] HEAD - refs/publish/master/pools_admin_ddt_tests
devstack@ubuntu:/opt/stack/neutron-lbaas/neutron_lbaas/tests/tempest/v2/scenario$
devstack@ubuntu:/opt/stack/neutron-lbaas/neutron_lbaas/tests/tempest/v2/scenario$
devstack@ubuntu:/opt/stack/neutron-lbaas/neutron_lbaas/tests/tempest/v2/scenario$
devstack@ubuntu:/opt/stack/neutron-lbaas/neutron_lbaas/tests/tempest/v2/scenario$
tox -e tempest
tempest develop-inst-nodeps: /opt/stack/neutron-lbaas
tempest runtests: PYTHONHASHSEED='3706390691'
tempest runtests: commands[0] | sh tools/pretty_tox.sh
running testr
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1}
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
${PYTHON:-python} -m subunit.run discover -t ./
${OS_TEST_PATH:-./neutron_lbaas/tests/unit}
{0}
neutron_lbaas.tests.tempest.v2.api.test_health_monitors.TestHealthMonitors.test_create_health_monitor
[11.086096s] ... ok
{0}
neutron_lbaas.tests.tempest.v2.api.test_health_monitors.TestHealthMonitors.test_create_health_monitor_extra_attribute
[0.013065s] ... ok
{0}
neutron_lbaas.tests.tempest.v2.api.test_health_monitors.TestHealthMonitors.test_create_health_monitor_invalid_attribute
[0.033716s] ... ok
{0}
neutron_lbaas.tests.tempest.v2.api.test_health_monitors.TestHealthMonitors.test_create_health_monitor_missing_attribute
[0.020612s] ... ok
{0}
neutron_lbaas.tests.tempest.v2.api.test_health_monitors.TestHealthMonitors.test_delete_health_monitor
[10.916318s] ... ok
{0}
neutron_lbaas.tests.tempest.v2.api.test_health_monitors.TestHealthMonitors.test_get_health_monitor
[11.037575s] ... ok
{0}
neutron_lbaas.tests.tempest.v2.api.test_health_monitors.TestHealthMonitors.test_list_health_monitors_empty
[0.062835s] ... ok
{0}
neutron_lbaas.tests.tempest.v2.api.test_health_monitors.TestHealthMonitors.test_list_health_monitors_one
[10.991776s] ... ok
{0}
neutron_lbaas.tests.tempest.v2.api.test_health_monitors.TestHealthMonitors.test_list_health_monitors_two
[44.915230s] ... ok
{0}
neutron_lbaas.tests.tempest.v2.api.test_health_monitors.TestHealthMonitors.test_udpate_health_monitor_invalid_attribute
[10.893886s] ... ok
{0}
neutron_lbaas.tests.tempest.v2.api.test_health_monitors.TestHealthMonitors.test_update_health_monitor
[21.516263s] ... ok
{0}
neutron_lbaas.tests.tempest.v2.api.test_health_monitors.TestHealthMonitors.test_update_health_monitor_extra_attribute
[11.019241s] ... ok
{0}
neutron_lbaas.tests.tempest.v2.api.test_listeners.ListenersTestJSON.test_create_listener
[11.068447s] ... ok
{0}
neutron_lbaas.tests.tempest.v2.api.test_listeners.ListenersTestJSON.test_create_listener_empty_admin_state_up
[0.123651s] ... ok
{0}
neutron_lbaas.tests.tempest.v2.api.test_listeners.ListenersTestJSON.test_create_listener_empty_connection_limit
[0.163494s] ... ok
{0}
neutron_lbaas.tests.tempest.v2.api.test_listeners.ListenersTestJSON.test_create_listener_empty_description
[11.030286s] ... ok
{0}
neutron_lbaas.tests.tempest.v2.api.test_listeners.ListenersTestJSON.test_create_listener_empty_load_balancer_id
[0.127011s] ... ok
{0}
neutron_lbaas.tests.tempest.v2.api.test_listeners.ListenersTestJSON.test_create_listener_empty_name
[11.307731s] ... ok
{0}
Re: [openstack-dev] [Neutron][LBaaS] Jenkins CI failure for patch: https://review.openstack.org/180019
Madhu, There have been problems with Gerrit all day. And, trying the link to you review, the service is now down. Consider letting the infra folks work the problem some more, look for a posting from them, or watch the topic messages on IRC and hold off on resubmitting until you see an all clear from Infra somewhere. --Rocky From: Madhusudhan Kandadai [mailto:madhusudhan.openst...@gmail.com] Sent: Monday, May 11, 2015 17:16 To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [Neutron][LBaaS] Jenkins CI failure for patch: https://review.openstack.org/180019 Hello, I am seeing odd behavior with Jenkins CI for the patch: https://review.openstack.org/180019 A quick background: 1. I could see all the tests passing on my virtual box and have attached the logs for your ready reference. 2. Whereas in Jenkins, I could see the different behavior which is not reproducible on my virtual box. I have tried the following to make it succeed. (a) 'recheck' comment - Jenkins reported unhappy. (b) restacked my devstack instance on my vm and run 'tox -e tempest', it succeeds on virtual box, but not for Jenkins. Not sure of the exact problem though, but would like to have community help on the same. Thanks! Madhu __ 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
