Got the message below this morning about a pipeline from 3 weeks ago that failed.  However, if you click the link on the pipeline, it actually passed 3 weeks ago but had failed before.  (I think I had forgotten to restart my runners after a system update on that machine.)

I got a similar message yesterday for the same pipeline.  I think I've gotten a couple others recently, that I ignored, thinking I forgot to start the runners again.

I don't remember getting such erroneous messages before, but my memory is not so good.

Not sure if there's anything to be done, but I thought I'd bring it up in case some config or something got messed up in the recent move of the host.  (Which has been working fine for me now.  Thanks!)

---------- Forwarded message ---------
From: GitLab <gitlab@common-lisp.net>
Date: Sun, Jan 26, 2025 at 5:00 AM
Subject: cmucl | Failed pipeline for master | adac84ea
To: <toy.raymond@gmail.com>


GitLab
✖ Pipeline #11421 has failed!
 
Project cmucl / cmucl
Branch
master
Commit
adac84ea
Merge branch 'issue-360-add-site-init' into 'ma...
Commit Author
Raymond Toy
 
Pipeline #11421 triggered by Raymond Toy
had 3 failed jobs
Failed jobs
✖ install
osx:install
✖ install
opensuse:install
✖ install
linux:install
GitLab
You're receiving this email because of your account on gitlab.common-lisp.net. Manage all notifications · Help


--
Ray