GitLab runners having issues
hecate at glitchbra.in
Wed Nov 9 08:24:51 UTC 2022
Thanks for the update Bryan!
Le 09/11/2022 à 09:22, Bryan Richter via ghc-devs a écrit :
> It looks like this was "resolved" -- it was an intermittent issue that
> went away on its own. I will start tracking it appropriately.
> Speaking of which, tracking spurious failures is not functioning right
> now, due to a problem with the ghc-perf-import bot. Until that gets
> resolved (later today, no doubt!), we'll see a higher pipeline failure
> On Tue, Nov 8, 2022 at 1:01 PM Bryan Richter <bryan at haskell.foundation> wrote:
>> Hi everyone,
>> Unfortunately, many CI jobs are failing for similar reasons on a
>> number of runners. Examples:
>> Running /usr/local/bin/cabal update --index=2020-12-21T14:48:20Z...
>> Downloading the latest package list from hackage.haskell.org
>> Version of <repo>/root.json is less than the previous version
>> /usr/local/bin/cabal update --index=2020-12-21T14:48:20Z failed
>> error: cabal update failed
>> -- https://gitlab.haskell.org/ghc/ghc/-/jobs/1224391
>> ERROR: Job failed: failed to pull image
>> -- https://gitlab.haskell.org/ghc/ghc/-/jobs/1224641
>> Moritz, can you look into these?
>> Could it have something to do with the GitLab emergency upgrade that
>> happened yesterday? Or were the runners reconfigured in some way?
>> I don't have administrative access to these runners.
>> I have created an issue: https://gitlab.haskell.org/ghc/ghc/-/issues/22422
> ghc-devs mailing list
> ghc-devs at haskell.org
More information about the ghc-devs