AArch64/Darwin CI troubles

Hi all, It has come to my attention that all of our AArch64/Darwin CI runners are currently inexplicably unavailable. I have made some inqueries but until this is resolved I'm afraid CI will be rather stuck. I'll keep the list updated as I learn more. Cheers, - Ben

I just looked at the simspace ones and while they were offline it was only
due to the known router loop problem and I believe the fix I found for
chreekat has restored them.
It began occurring with a wireguard-tools upgrade and while should track
down the cause of the bad route it only shows up on restarts.
On Fri, Mar 15, 2024 at 7:12 PM Ben Gamari
Hi all,
It has come to my attention that all of our AArch64/Darwin CI runners are currently inexplicably unavailable. I have made some inqueries but until this is resolved I'm afraid CI will be rather stuck. I'll keep the list updated as I learn more.
Cheers,
- Ben _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

I've brought one runner back. I"ll check on the others in a few hours, and
also check if the runner misbehaves.
On Sat, 16 Mar 2024 at 08:36, davean
I just looked at the simspace ones and while they were offline it was only due to the known router loop problem and I believe the fix I found for chreekat has restored them. It began occurring with a wireguard-tools upgrade and while should track down the cause of the bad route it only shows up on restarts.
On Fri, Mar 15, 2024 at 7:12 PM Ben Gamari
wrote: Hi all,
It has come to my attention that all of our AArch64/Darwin CI runners are currently inexplicably unavailable. I have made some inqueries but until this is resolved I'm afraid CI will be rather stuck. I'll keep the list updated as I learn more.
Cheers,
- Ben _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Created fresh repository.
12 https://gitlab.haskell.org/tbidne/ghc/-/jobs/1809168#L12remote: You
are not allowed to download code from this project.
13 https://gitlab.haskell.org/tbidne/ghc/-/jobs/1809168#L13fatal: unable
to access 'https://gitlab.haskell.org/tbidne/ghc.git/': The requested URL
returned error: 403
This is a problem. I guess we should lock the runners to the ghc project
only.
On Sat, 16 Mar 2024 at 09:53, Moritz Angermann
I've brought one runner back. I"ll check on the others in a few hours, and also check if the runner misbehaves.
On Sat, 16 Mar 2024 at 08:36, davean
wrote: I just looked at the simspace ones and while they were offline it was only due to the known router loop problem and I believe the fix I found for chreekat has restored them. It began occurring with a wireguard-tools upgrade and while should track down the cause of the bad route it only shows up on restarts.
On Fri, Mar 15, 2024 at 7:12 PM Ben Gamari
wrote: Hi all,
It has come to my attention that all of our AArch64/Darwin CI runners are currently inexplicably unavailable. I have made some inqueries but until this is resolved I'm afraid CI will be rather stuck. I'll keep the list updated as I learn more.
Cheers,
- Ben _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

I've been unavailable for the last week, which means I haven't been on hand
to babysit the runners. My first priority is to finish the Stackage
migration, which is why I haven't taken more decisive action with the
runners already. I haven't had the bandwidth.
I'll be back on Monday, and the acute stage of the Stackage migration now
only involves waiting passively for a huge data transfer to complete.
Making a more robust CI platform is probably the most important thing I can
do next.
On Sat, 16 Mar 2024, 6.17 Moritz Angermann,
Created fresh repository. 12 https://gitlab.haskell.org/tbidne/ghc/-/jobs/1809168#L12remote: You are not allowed to download code from this project. 13 https://gitlab.haskell.org/tbidne/ghc/-/jobs/1809168#L13fatal: unable to access 'https://gitlab.haskell.org/tbidne/ghc.git/': The requested URL returned error: 403
This is a problem. I guess we should lock the runners to the ghc project only.
On Sat, 16 Mar 2024 at 09:53, Moritz Angermann
wrote: I've brought one runner back. I"ll check on the others in a few hours, and also check if the runner misbehaves.
On Sat, 16 Mar 2024 at 08:36, davean
wrote: I just looked at the simspace ones and while they were offline it was only due to the known router loop problem and I believe the fix I found for chreekat has restored them. It began occurring with a wireguard-tools upgrade and while should track down the cause of the bad route it only shows up on restarts.
On Fri, Mar 15, 2024 at 7:12 PM Ben Gamari
wrote: Hi all,
It has come to my attention that all of our AArch64/Darwin CI runners are currently inexplicably unavailable. I have made some inqueries but until this is resolved I'm afraid CI will be rather stuck. I'll keep the list updated as I learn more.
Cheers,
- Ben _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
participants (4)
-
Ben Gamari
-
Bryan Richter
-
davean
-
Moritz Angermann