I'm not like broken state. It's really annoying kicking manually rebuilds & fail state because of remote api delays.
I expect scheduler/workers continue build when upstream project appears.
What about delay state and freeze state for project in case remote api errors?
On 11.06.2013, at 18:47, Michael Schroeder
On Tue, Jun 11, 2013 at 04:57:43PM +0200, Adrian Schröter wrote:
Am Dienstag, 11. Juni 2013, 14:34:00 schrieb Magnus Lewis-Smith:
My local OBS is not able to build anything at the moment. I notice that the scheduler logs are filling with 'rpc timeout' errors
We see that as well and we saw this caused by a bunch of large requests eating our IO (storage and network).
FYI: The cause of this is currently not known, maybe it has something to do with the migration of our storage space we did two weeks ago. Our storage expert is currently on vacation, though.
Cheers, Michael.
-- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org