The fedora-notif bot has been very laggy (usually days) since the move to libera. Looking at my IRC logs going back to the beginning of the move, it appears to average a little over 24 hours behind., though I have seen it as little as 6 hours, currently we are running over 48 hours. Examples below taken from local IRC logs:
Jun 05 06:35:46 .:fedora-notif:. jforbes's kernel-5.12.9-200.fc33 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=1758472 This build actually completed June 3 11:46 local time.
Jun 18 15:35:50 .:fedora-notif:. sgallagh[m] raised a point of information in the "Fedora ELN SIG (2021-06-18)" meeting in #fedora-meeting: "AWS images are in the works for ELN" an hour ago None The actual point was raised: Jun 18 11:17:52 .:+sgallagh[m]:. #info AWS images are in the works for ELN
Jul 01 12:31:34 .:fedora-notif:. jforbes's kernel-5.12.14-300.fc34 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=1776962 Build actually completed Jun 30 at 15:48 local time
Jul 08 20:50:13 .:fedora-notif:. jforbes's kernel-5.12.15-300.fc34 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=1778524 Build actually completel Jul 07 at 17:15 local time
Jul 13 14:22:15 .:fedora-notif:. cmurf linked to more information in the "Fedora QA meeting" meeting in #fedora-meeting: "https://bugzilla.redhat.com/show_bug.cgi?id=1976653" None Actual link was dropped: Jul 12 10:29:49 .:cmurf:. https://bugzilla.redhat.com/show_bug.cgi?id=1976653
Jul 16 08:58:29 .:fedora-notif:. jforbes's kernel-5.14.0-0.rc1.20210713git7fef2edf7cc7.18.fc35 started building http://koji.fedoraproject.org/koji/buildinfo?buildID=1780404 Actual build start time was Jul 13 17:01 local time.
Metadata Update from @humaton: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: dev, medium-gain, medium-trouble
Is this better now? It seems a little behind now still, but not too bad...
Not sure, I only did 2 builds today, both started about 7 hours ago, but I have not seen any messages from the notif bot for either the build start or completion.
It looks like it's still about a day or day and a half behind. ;(
13 hours behind now. Slowly catching up.
So, it's about 20min behind right now, but thats only because it got stuck and I restarted it again.
So, hopefully this is reasonable enough for now, and I am hoping the python3 version we are testing now can handle things better.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
This does seem to be much better so far today.
Login to comment on this ticket.