Unit test jobs (py35) fails with timeout often

[Slawek Kaplonski]

It happens quite often recently.
Examples of failures:
http://logs.openstack.org/58/565358/14/check/openstack-tox-py35/aa30b12/job-output.txt.gz or http://logs.openstack.org/03/563803/9/check/openstack-tox-py35/a50de4a/job-output.txt.gz

[Miguel Lavalle (minsel)]

In preparation for today's CI meeting, I spent some time looking for instances of this bug this morning. Couldn't find any. Discussed it also during the meeting and nobody has seen it lately

[Slawek Kaplonski (slaweq)]

I just checked it on logstach with query like:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=(build_name%3A%5C%22openstack-tox-py35%5C%22%20OR%20build_name%3A%5C%22openstack-tox-py27%5C%22)%20AND%20message%3A%5C%22RUN%20END%20RESULT_TIMED_OUT%5C%22%20AND%20project%3A%5C%22openstack%2Fneutron%5C%22

and I found 8 hits during last week. I happens in both py27 and py35 jobs.

[Slawek Kaplonski (slaweq)]

From short analysis it looks for me that some tests are running much longer in failed runs then in "good" runs. I will need to compare all of results to be sure that this slowdown could cause such issue.

[Slawek Kaplonski (slaweq)]

As we don't have py35 job anymore, I will close this bug as won't fix.