CI on forked projects: Darwin woes

[Carter Schonwald]

I’m the root care taker on the Mac ci box.

One issue here is that while  forks and branches both get ci, only branches
are visible to non admin roles. So there could be a kajillion other folks
forks going on or something.

timeouts sound like gitlab side thing.  I definitely have had to restart
jobs before.

For what it’s worth: it’s hosted at Mac stadium so it’s actually in a data
center.  Plus after Ben added some disk space cleanup scripts to the ci its
had zero administrative interventions for months.  Plus it’s configured to
actually have a working gitlab runner even if a reboot happens (took a
while to figure out that bit of Mac admin )

Failures on the Mac mini side tend to have more informative failure modes.
Timeouts are a gitlab runner thing. And I’ve definitely had to tickle
restarting in my own patches.

Next time you hit a failure could you share with the devs list and or #ghc
irc ?

On Wed, May 8, 2019 at 2:59 PM Iavor Diatchki <iavor.diatchki at gmail.com>
wrote:

> I think there was the ghc-devops-group list, but I don't know if it is
> still active, and I kind of like to not have to follow too many lists.
>
> For example, I had also not realized that it is an option to push to
> branches on the main project, and have been using my own fork,
> so thanks for posting this here!
>
> -Iavor
>
>
> On Wed, May 8, 2019 at 11:40 AM Kevin Buhr <buhr at asaurus.net> wrote:
> >
> > Over the past few days, I've submitted several merge requests from
> > branches on my forked project (mostly because I didn't even realize
> > pushing to a branch on the main project was an alternative).
> >
> > When those MRs run under CI, I've had a bunch of failures due to
> > timeouts waiting on a darwin-x86_64 runner.  I was a little mystified
> > that no other pipelines besides mine seemed to be having this problem,
> > but I've come to understand that MRs submitted from branches on the main
> > project use a different, larger set of runners than the shared runners
> > used by MRs from branches on forked projects.
> >
> > Under my project, I can view the available shared runners under the
> > "Settings" -> "CI/CD" -> "Runners" tab, and the problem seems to be that
> > there's only one darwin runner ("b4bc6410" /
> > mac-mini-x86_64-darwin-davxkc).  This machine is a trooper, but it
> > unfortunately shares a circuit breaker with a toaster oven, so it goes
> > offline every time someone wants a bagel, and the rest of the time it
> > must be running CI for a few hundred GHC forks.
> >
> > I ended up deleting an (unreviewed) MR sourced from my branch, and
> > pushing it to the main project and resubmitting just to get the CI to
> > run.  (Admittedly, it failed, but at least not on darwin!)  I obviously
> > don't want to do this with the merge requests that have already been
> > reviewed.
> >
> > Is this a temporary problem?  Is there anything I can do other than keep
> > retrying the darwin jobs every couple days?
> >
> > Also, is there a better place than "ghc-dev" to send these sorts of
> > GitLab/CI issues?  I thought there might be a project dedicated to it,
> > but if so I couldn't find it.
> >
> >
> > --
> > Kevin Buhr <buhr at asaurus.net>
> >
> > _______________________________________________
> > ghc-devs mailing list
> > ghc-devs at haskell.org
> > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20190512/ee4973ce/attachment.html>