[openstack-dev] [mistral] Help with test run

Clark Boylan cboylan at sapwetik.org
Tue May 1 16:11:51 UTC 2018

On Fri, Apr 27, 2018, at 2:22 AM, András Kövi wrote:
> Hi,
> Can someone please help me with why this build ended with TIMED_OUT?
> http://logs.openstack.org/85/527085/8/check/mistral-tox-unit-mysql/3ffae9f/

Reading the job log the job setup only took a few minutes. Then the unittests start and are running continuously until the timeout happens at 30 minutes. Chances are that the default 30 minute timeout is not sufficient for this job. Runtime may vary based on cloud region and presence of noisy neighbors.

As for making this more reliable you can increase the timeout in the job configuration for that job. Another approach would be to make the unittests run more quickly. I notice the job is hard coded to use concurrency=1 when invoking the test runner so you are only using ~1/8 of the available cpus. You might try increasing this value though will likely need to make sure the tests don't conflict with each other.


More information about the OpenStack-dev mailing list