Re: CI on forked projects: Darwin woes

Yeah. That’s my current theory. It doesn’t help that the queue length isn’t visible On Mon, May 13, 2019 at 8:43 AM Ben Gamari wrote:

Carter Schonwald writes:

...

Cool. I recommend irc and devs list plus urls / copies of error messages.

Hard to debug timeout if we don’t have the literal url or error messages shared !

For what it's worth I suspect these timeouts are simply due to the fact that we are somewhat lacking in Darwin builder capacity. There are rarely fewer than five builds queued to run on our two Darwin machines and this number can sometimes spike to much higher than the machines can run in the 10-hour build timeout.

Cheers,

- Ben