yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #70527
[Bug 1744983] [NEW] coverage job fails with timeout
Public bug reported:
It happened in Ocata: http://logs.openstack.org/41/532941/1/gate
/openstack-tox-cover/5a26283/job-
output.txt.gz#_2018-01-22_23_39_21_734729
2018-01-22 23:02:09.046252 | ubuntu-xenial | load_tests = test_base.optimize_db_test_loader(__file__)
2018-01-22 23:39:21.734729 | RUN END RESULT_TIMED_OUT: [untrusted : git.openstack.org/openstack-infra/zuul-jobs/playbooks/tox/run.yaml@master]
It took at least 37 minutes for coverage report to run.
In a good run from the same branch, we can see that the same tox run
took ~18 minutes: http://logs.openstack.org/61/532461/1/gate/openstack-
tox-cover/2ebf0d6/job-output.txt.gz#_2018-01-17_10_27_36_867873
2018-01-17 10:27:36.867873 | ubuntu-xenial | load_tests = test_base.optimize_db_test_loader(__file__)
2018-01-17 10:45:02.053109 | ubuntu-xenial | running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
There are no leads in logs. I am also not sure whether the failure
affects other branches.
** Affects: neutron
Importance: Medium
Status: Confirmed
** Tags: gate-failure unittest
** Changed in: neutron
Importance: Undecided => Medium
** Changed in: neutron
Status: New => Confirmed
** Tags added: gate-failure unittest
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1744983
Title:
coverage job fails with timeout
Status in neutron:
Confirmed
Bug description:
It happened in Ocata: http://logs.openstack.org/41/532941/1/gate
/openstack-tox-cover/5a26283/job-
output.txt.gz#_2018-01-22_23_39_21_734729
2018-01-22 23:02:09.046252 | ubuntu-xenial | load_tests = test_base.optimize_db_test_loader(__file__)
2018-01-22 23:39:21.734729 | RUN END RESULT_TIMED_OUT: [untrusted : git.openstack.org/openstack-infra/zuul-jobs/playbooks/tox/run.yaml@master]
It took at least 37 minutes for coverage report to run.
In a good run from the same branch, we can see that the same tox run
took ~18 minutes: http://logs.openstack.org/61/532461/1/gate
/openstack-tox-cover/2ebf0d6/job-
output.txt.gz#_2018-01-17_10_27_36_867873
2018-01-17 10:27:36.867873 | ubuntu-xenial | load_tests = test_base.optimize_db_test_loader(__file__)
2018-01-17 10:45:02.053109 | ubuntu-xenial | running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
There are no leads in logs. I am also not sure whether the failure
affects other branches.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1744983/+subscriptions
Follow ups