On Wed, 30 Jul 2025 at 12:12, Bryan Richter <bryan@haskell.foundation> wrote:
(Sorry for spamming emails)I should also mention that the large number of "spurious failures" on the linked dashboard is, itself, a spurious result. These errors are *not* spurious, but they are being treated as such. That causes up to 10 needless retries per failure. That's something I have on my list to fix.Stll, even after dividing by 10, there are a lot of failures.On Wed, 30 Jul 2025 at 14:09, Bryan Richter <bryan@haskell.foundation> wrote:I'm loathe to pause a lint runner, but I will do so in this case, to see if the problem is localized to that system.On Wed, 30 Jul 2025 at 14:08, Bryan Richter <bryan@haskell.foundation> wrote:It looks like most lint jobs are failing because they want to run on a Docker image that is missing from the GitLab registry. I know Ben talked about having some scheme for expiring images. I don't think that has been put into place, however.There could also just be fallout from the server migration, even though that took place a few months ago. I have seen more of these types of failures since then.Since I haven't touched the ci-images repo recently, somebody else will need to look at this.fwiw it does look like a primary victim is the "OpenCape lint runner", as seen here: https://grafana.gitlab.haskell.org/d/167r9v6nk/ci-spurious-failures?orgId=2&from=now-30d&to=now&var-types=$__all&var-runners=OpenCape%20lint%20runner&var-jobs=$__all&refresh=15m&timezone=browserOn Wed, 30 Jul 2025 at 11:15, Simon Peyton Jones <simon.peytonjones@gmail.com> wrote:Dear GHC devsThis mr !10479 seems Utterly Broken. Looks as if something is wrong with CI. Can anyone help?ThanksSimon_______________________________________________On Wed, 30 Jul 2025 at 09:05, GitLab <gitlab@gitlab.haskell.org> wrote:
You're receiving this email because of your account on gitlab.haskell.org. Manage all notifications · Help
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
