Re: CI on forked projects: Darwin woes
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 ! -Carter ________________________________ From: Kevin Buhr <buhr@asaurus.net> Sent: Sunday, May 12, 2019 11:01 AM To: Carter Schonwald Cc: Iavor Diatchki Subject: Re: CI on forked projects: Darwin woes Thanks! I'll send a note if it starts happening again. On 5/12/19 7:23 AM, Carter Schonwald wrote:
[ . . . ]
Next time you hit a failure could you share with the devs list and or #ghc irc ?
-- Kevin Buhr <buhr@asaurus.net>
Carter Schonwald <carter.schonwald@gmail.com> 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
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 <ben@smart-cactus.org> wrote:
Carter Schonwald <carter.schonwald@gmail.com> 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
participants (2)
-
Ben Gamari -
Carter Schonwald