Comment 1 for bug 1766703

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

OK runs:

Checked on:
http://logs.openstack.org/07/560907/3/check/neutron-rally-neutron/1bc15fb/
http://logs.openstack.org/84/561384/8/check/neutron-rally-neutron/7568c06/
http://logs.openstack.org/27/533327/15/check/neutron-rally-neutron/f879e5e/
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:
http://logs.openstack.org/27/445827/26/check/neutron-rally-neutron/a461f3d/
http://logs.openstack.org/24/558724/11/check/neutron-rally-neutron/d891678/
http://logs.openstack.org/90/545490/9/check/neutron-rally-neutron/9de921a/
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....