quicklisp-projects
quicklisp-projects copied to clipboard
quicklisp
Please add machine-state
This library implements various functions to access status information about the machine, process, etc.
Author: Yukari Hafner License: zlib Documentation: https://shinmera.github.io/machine-state/ Source: https://github.com/Shinmera/machine-state.git
Failure log here: http://report.quicklisp.org/2023-11-29/failure-report/machine-state.html
This is, just like tooter, stuck on a commit that no longer exists. The failure does not occur on current HEAD of the main branch.
Please make sure repositories aren't updated via git pull but rather via git fetch origin && git reset --hard origin/main.
git pull is liable to get stuck on commits that are force-pushed away.
Hmm, I get this error on a fresh checkout with a git clone. I'm on commit
5ff77bf7dcd0b7d9ab66deb46e52ce1464eab285. What should I be on instead?
On Thu, Nov 30, 2023 at 3:12 AM Yukari Hafner @.***> wrote:
This is, just like tooter, stuck on a commit that no longer exists. The failure does not occur on current HEAD of the main branch.
— Reply to this email directly, view it on GitHub https://github.com/quicklisp/quicklisp-projects/issues/2377#issuecomment-1833288882, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACPNLOB4GJ6XDNMQATJRBDYHA5XXAVCNFSM6AAAAAA7WBUGXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZTGI4DQOBYGI . You are receiving this because you commented.Message ID: @.***>
Ok, thanks, I'll investigate locally some more.
On Thu, Nov 30, 2023 at 6:01 AM Yukari Hafner @.***> wrote:
That's the correct commit, but I'm not getting a failure on SBCL-2.3.10.
— Reply to this email directly, view it on GitHub https://github.com/quicklisp/quicklisp-projects/issues/2377#issuecomment-1833535558, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACPNLO3PSXPUZWQ7RTPLITYHBRPHAVCNFSM6AAAAAA7WBUGXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZTGUZTKNJVHA . You are receiving this because you commented.Message ID: @.***>
Looking into it, the failure report seems accurate. Not sure why it's not triggered in 2.3.10. I pushed a fix now.