Melpa CI not functioning?

[Boruch-Baum]

The melpa database doesn't seem to have been rebuilt for about three days now. When I perform a packages update from within Emacs, the most recent update is from 24 January, and on the melpa website the box on the upper right corner reads "Next build: 3 days ago, last ended 3 days ago and took 2 hours".

[milkypostman]

Thanks for reporting. Will poke around a bit on the server and see what's up.

[milkypostman]

Should be fixed now. Although I am having problems with the "last update" json file being stale with Safari.

[Boruch-Baum]

Good news, bad news: Performing a package update on my local Emacs does show packages updated today; The MELPA website does not reflect those updates. For example, package blamer was updated earlier today and displays as such in the *Packages* buffer, but the website database shows its most recent update on Jan 17. (Firefox-esr v115)

[Boruch-Baum]

I just peeked at the MELPA stable web page and it has a slightly different issue. There, the update box isn't stuck four days ago. It says that the current build started 22 minutes ago.

[Boruch-Baum]

Never mind. I needed to clear my web browser cache and refresh the page. Everything seems to be working fine. Sorry about the "signal/noise ratio".

[jcs090218]

@milkypostman I reckon the MELPA Stable has this issue as well. I've released a tag, but it hasn't been updated for over 12 hours. But I'm not sure since MELPA Stable used to take longer (?). 🤔

[milkypostman]

@jcs090218 can you tell me which package and I'll investigate?

[jcs090218]

Package eask, it should be version 0.9.4.

[Boruch-Baum]

Yeah, I also seem to be seeing a repeat of the original problem. Both MELPA and MELPA stable are reporting not having been built for 10 hours.

…

On 2024-01-28 15:41, Jen-Chieh Shen wrote: Package [1]eask, it should be version 0.9.4. — Reply to this email directly, [2]view it on GitHub, or [3]unsubscribe. You are receiving this because you modified the open/close state. Message ID: ***@***.***> References 1. https://stable.melpa.org/#/eask 2. #8901 (comment) 3. https://github.com/notifications/unsubscribe-auth/AAOE3KEP65XZKIELGGQUA6DYQ3O3LAVCNFSM6AAAAABCNW7KCCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJTG43DEMRWGA

-- hkp://keys.gnupg.net CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0

[milkypostman]

Looks like the build logs completely filled our main drive. I had to truncate the log files and fixed the docker config. Let's let it run a few days and I'll leave this bug open to check back in.

[milkypostman]

I committed 6ced110 with some notes for myself and the config I set up so I remember to do this setup next time we update our servers.

[swflint]

At least one new package (org-cite-overlay, #8915) does not appear to be built and on the MELPA sight. Could it be a similar cause?

[milkypostman]

Is it possible that source hut has blocked our IP? I cannot seem to get it to clone the repro at all. It just hangs from our server.

[milkypostman]

#8920 is tracking the issue.