On 08/08/2014 09:37 AM, Andreas Jaeger wrote: > What kind of timeout do you mean? A timeout to reach the OpenStack > infrastructure or a timeout in one of the tests? Not sure. I think in the infrastructure. > For the former, one low-tech solution would be to create a bug that you > could reference. If elastic research would be able to find this > condition, it would be even better... Example: https://review.openstack.org/#/c/112767/ FAILED: http://logs.openstack.org/67/112767/1/check/gate-config-puppet-syntax/43772a5/console.html SUCCESS: http://logs.openstack.org/67/112767/1/check/gate-config-puppet-syntax/15bf4a1/console.html ---snip--- 2014-08-08 06:18:37.941 | + git clone file:///opt/git/openstack-infra/config . 2014-08-08 06:18:40.641 | Cloning into '.'... 2014-08-08 06:19:08.369 | + git remote set-url origin git://git.openstack.org/openstack-infra/config 2014-08-08 06:19:08.375 | + git remote update 2014-08-08 06:19:08.383 | Fetching origin 2014-08-08 06:48:30.921 | Build timed out (after 30 minutes). Marking the build as failed. 2014-08-08 06:48:30.928 | Build was aborted ---snap--- Not sure what to put into the bug report because I cannot see any details in the logs. Christian. -- Christian Berendt Cloud Computing Solution Architect Mail: berendt at b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537