Rally tests job is reaching job timeout often

Bug #1766703 reported by Slawek Kaplonski on 2018-04-24
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

In about 20-30% of runs neutron-rally-neutron job fails because global job's timeout is reached.
Example failed runs:
* http://logs.openstack.org/24/558724/11/check/neutron-rally-neutron/d891678/job-output.txt.gz
* http://logs.openstack.org/90/545490/9/check/neutron-rally-neutron/9de921a/job-output.txt.gz

Slawek Kaplonski (slaweq) wrote :

I compared execute time for 3 good and 3 failed job runs.

OK runs:

Checked on:
Start End
2018-04-17 14:27:01 2018-04-17 15:57:03
2018-04-19 08:25:18 2018-04-19 09:50:06
2018-04-25 17:43:54 2018-04-25 19:12:14
About 1:25-1:30h

Failed runs:

Failed runs checked:
Start End (timeout at)
2018-04-03 08:41:40 2018-04-03 10:44:06
2018-04-24 03:07:21 2018-04-24 05:07:45
2018-04-23 23:28:28 2018-04-24 01:30:24
Failed after 2 hours

So I looks that there is something wrong sometimes. I will try to investigate it more still....

Changed in neutron:
assignee: nobody → Slawek Kaplonski (slaweq)
Changed in neutron:
assignee: Slawek Kaplonski (slaweq) → nobody
Slawek Kaplonski (slaweq) wrote :

I can't find recent data with such issues. I also didn't noticed such issues recently in jobs which I was checking. So I think that we can for now close this bug and reopen if it will be necessary in the future.

Changed in neutron:
status: Confirmed → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for neutron because there has been no activity for 60 days.]

Changed in neutron:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers