Robin Shen [10/Dec/15 12:27 AM] Please check size of your build log, QB can be busy on transferring build logs if it is large and if there are many builds running. Also please check if you have custom scripts running in post-execute actions of your master step.

David Keane [10/Dec/15 11:21 AM] Hi Robin,    A litte more information for you. These builds runs on a schedule at night also and I can see from the run last night that the times are correct. The only difference here would be the load on the server as at night only these builds would be running. This suggest that the load on the server is causing this. Is there anyway I can fix this as we are using these timings for metrics and right now this is not possible. Davis

David Keane [10/Dec/15 04:55 PM] The build log is 107MB . There are no post execute steps on the master

Robin Shen [11/Dec/15 12:19 AM] If you have many builds running together and if many of them are uploading large logs like this, the server IO might be busy. If some of the builds are downloading/publishing artifacts to server, the situation can be even worse. I'd recommend to tune your build log level to make it generate less log. To do it, edit general setting of your configuration, and specify build log level as WARN. Also it is worth to store artifacts on agent if server IO is quite busy: http://wiki.pmease.com/display/QB60/Store+Build+Artifacts+on+Agent