2026-03-01 18:11:33 <achill> on it
2026-03-01 18:15:43 <ikke> algitbot: ok, thanks
2026-03-01 18:15:46 <ikke> achill: *
2026-03-01 18:15:54 <achill> yup
2026-03-01 18:17:10 <PureTryOut> Strange, it succeeded on CI 😅
2026-03-01 18:17:22 <PureTryOut> Ah you literally just merged the glslang update, ok
2026-03-01 18:20:05 <achill> yeah :))
2026-03-01 18:20:20 <achill> and my MR rebuild doesn't get any runners :((
2026-03-01 18:20:36 <achill> all already busy
2026-03-01 18:22:39 <ikke> Hmm
2026-03-01 18:28:27 <ikke> There should be plenty of space for the smaller jobs, but they are not picked up
2026-03-01 18:44:04 <achill> amend-commit and force push worked /shrug
2026-03-02 11:12:15 <achill> algitbot: retry master
2026-03-02 12:47:14 <omni> algitbot: retry master
2026-03-03 08:17:24 <Ariadne> algitbot: retry master
2026-03-03 08:17:28 <Ariadne> algitbot: retry master
2026-03-03 08:17:38 <Ariadne> hmm, s390x is out to lunch?
2026-03-04 16:10:46 <achill> ikke: ^
2026-03-04 16:16:33 <ikke> achill: tailscale?
2026-03-04 16:16:37 <achill> yea
2026-03-04 16:16:40 <ikke> listen unix /home/buildozer/aports/community/tailscale/src/TestDoesNotOverwriteIrregularFiles465813604/001/TestDoesNotOverwriteIrregularFiles: bind: invalid argument
2026-03-04 16:28:08 <ikke> achill: the path is sus
2026-03-04 16:28:23 <ikke> tailscale/src/TestDoesNotOverwriteIrregularFiles3807131128
2026-03-04 16:28:55 <ikke> I guess it uses GOTMPDIR?
2026-03-04 16:42:44 <ikke> yes, it has to do with us overriding GOTMPDIR
2026-03-04 16:53:14 <ikke> achill: ah, apparently the path of unix sockets can be max 108 characters, and the tmpdir location makes it 130
2026-03-04 16:53:20 <ikke> https://stackoverflow.com/questions/79646557/is-there-any-restrictions-on-unix-socket-path-length
2026-03-04 16:54:35 <ikke> achill: I suppose we could use the same logic as the test does now for macos
2026-03-04 17:34:53 <ikke> lesigh
2026-03-04 19:10:37 <ikke> achill: The current test failure is due to go1.26
2026-03-04 19:11:05 <ikke> On my local build container, I still had 1.25.* and the test passed
2026-03-04 19:11:21 <ikke> There is some difference in httptest or something like that that makes it fail
2026-03-04 19:34:45 <ikke> d'oh, go 1.26.0 explicitly sets a DialContext now, which tailscale does not expect and panics
2026-03-04 19:58:41 <ikke> achill: so tailscale was never rebuilt against go 1.26..
2026-03-04 21:07:48 <ikke> algitbot: retry master
2026-03-04 21:11:46 <ikke> algitbot: retry master
2026-03-04 22:33:33 <andypost[m]> algitbot: retry master
2026-03-05 08:36:54 <omni> algitbot: retry master
2026-03-05 09:33:13 <omni> algitbot: retry master
2026-03-05 09:36:11 <omni> =(
2026-03-05 09:36:34 <omni> oh, OOM
2026-03-05 09:36:46 <omni> algitbot: retry master
2026-03-05 10:04:29 <omni> algitbot: retry master
2026-03-05 10:06:10 <omni> ikke: the aarch64 rust build got butchered by the OOM murderer again, is there anything that can be done to avoid that? like in CI
2026-03-05 10:13:12 <ikke> omni: https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/.gitlab/job-config.yaml
2026-03-05 10:15:41 <omni> ikke: does that also affect the package builders?
2026-03-05 10:15:52 <ikke> omni: no
2026-03-05 10:16:04 <ikke> If it fails on the builders, then it's actually OOM
2026-03-05 10:16:11 <ikke> (or address space)
2026-03-05 10:16:30 <omni> right
2026-03-05 10:17:48 <ikke> According to our monitoring, the amount of memory available on the aarch64 host has not been < 200GB
2026-03-05 10:19:21 <ikke> So I wonder why it says "out of memory"
2026-03-05 11:08:21 <omni> \o/
2026-03-05 11:08:41 <ikke> omni: still, would be good to find out why it even happens
2026-03-05 11:09:07 <ikke> On a server with 256GB of memory
2026-03-05 11:53:39 <omni> ikke: I was thinking too many concurrent jobs, and perhaps limiting that would help, but if you're saying it always had a lot of free memory idk...
2026-03-05 11:53:59 <omni> and it couldn't have peaked in memory usage between samples, right?
2026-03-05 11:54:48 <ikke> For a moment, the server went from ~64GB memory used to ~96GB. Not enough to end up in OOM land
2026-03-06 01:19:35 <huajingyun> algitbot: retry master
2026-03-06 17:41:37 <ikke> achill: bestline is in testing.l.
2026-03-06 17:41:39 <ikke> testing..
2026-03-06 17:41:42 <ikke> I was just working on a fix
2026-03-06 17:44:06 <achill> ikke: oh oops
2026-03-06 17:50:30 <ikke> Anoying tests: "expected false to be true"
2026-03-06 17:50:34 <ikke> Absolutely clear
2026-03-06 17:50:46 <ikke> How can you ever expect false to be true :P
2026-03-06 18:02:23 <ikke> ginkgo: https://github.com/onsi/ginkgo/issues/1640
2026-03-06 18:48:51 <andypost[m]> algitbot: retry master
2026-03-06 19:32:52 <ikke> sq: fails due to go vet complaining about %w not being supported by a function that adds support itself
2026-03-06 19:35:02 <ikke> grafana writes a response body in a test with a response code that does not allow one (1.26 added a check to disallow that)
2026-03-06 19:55:31 <ikke> lol: "crypto/tls bug: where's my session ticket?"
2026-03-07 10:10:26 <omni> wait, is aws-lc still failing only on arm?
2026-03-07 10:11:28 <omni> or.. it moved on on x86 at least..?
2026-03-07 10:12:10 <f_> seems like it https://build.alpinelinux.org/buildlogs/build-edge-x86/community/aws-lc/aws-lc-1.68.0-r1.log
2026-03-07 10:15:08 <omni> ok, perhaps there's some architecture specific reason for it not to Werror on x86..
2026-03-08 20:01:57 <omni> ikke: do you know what that "invalid cross-device link" for pulumi is about?
2026-03-08 20:02:08 <omni> perhaps not what it is failing on
2026-03-08 20:02:20 <omni> or due to
2026-03-08 20:03:11 <ikke> omni: My guess would be they try to create hardlinks across filesystems?
2026-03-08 20:03:29 <ikke> https://unix.stackexchange.com/questions/79132/invalid-cross-device-link-while-hardlinking-in-the-same-file-system
2026-03-08 20:05:07 <ikke> omni: or I guess in this case a rename (instead of move?)
2026-03-08 20:44:20 <omni> ikke: sure, but it must have worked at some point? this is supposed to just be a rebuild with newer go
2026-03-08 20:44:43 <omni> or is it fetching something that is not the same last time?
2026-03-08 20:45:08 <omni> last rebuild was a month a go
2026-03-08 20:51:47 <omni> how about we unbump it and wait for it to be sorted in !96438 ?
2026-03-08 21:05:11 <omni> !98728
2026-03-08 22:20:14 <omni> fossdd: I'd like to merge !98735 unless you have any objections
2026-03-08 22:20:37 <omni> it would be nice to let aarch64 and x86_64 upload to community/
2026-03-08 23:17:43 <omni> fossdd: sorry to not give you more time, I thought you were around since you had just gotten other things in
2026-03-08 23:28:14 <omni> !98737
2026-03-08 23:51:47 <omni> !98738
2026-03-09 00:29:15 <omni> !98741 !98742
2026-03-09 06:48:03 <ikke> omni: mio I don't have more time, but tofutf seems to be missing a trailing / in the URL, causing a 307
2026-03-09 06:48:26 <ikke> request: Path: "/api/v3/repos/acme/terraform/tarball",
2026-03-09 06:49:49 <ikke> resp header: Location: "/api/v3/repos/acme/terraform/tarball/",
2026-03-09 10:08:31 <omni> ikke: thanks! I don't have time either right now
2026-03-09 14:52:32 <mio> ikke: thanks for the hint, !98758
2026-03-09 21:27:03 <ikke> andypost[m]: thanks!
2026-03-09 21:27:27 <andypost[m]> home it faster then clean-up builders
2026-03-09 21:27:33 <andypost[m]> s/home/hope
2026-03-10 09:19:43 <PureTryOut> algitbot: retry master
2026-03-10 11:46:34 <ikke> PureTryOut: kitenarary test failure:
2026-03-10 11:46:36 <ikke>  -            "addressCountry": "DE",
2026-03-10 11:46:38 <ikke>  +            "addressCountry": "Deutschland",
2026-03-10 12:10:11 <PureTryOut> Ugh...
2026-03-10 13:57:19 <PureTryOut> algitbot: retry master
2026-03-11 06:09:52 <ikke> algitbot: retry master
2026-03-12 12:08:40 <ikke> I'm checking go-task (I've already have an upstream issue for it)
2026-03-12 12:52:09 <ikke> tests/env_test.py::CloseTest::test_close Fatal Python error: Segmentation fault
2026-03-12 17:03:58 <ikke> algitbot: retry master
2026-03-13 00:30:30 <mio> algitbot: retry 3.23-stable
2026-03-13 04:11:54 <mio> algitbot: retry 3.23-stable
2026-03-13 05:31:35 <mio> dotnet8-runtime maintainer notified
2026-03-13 06:06:41 <mio> algitbot: retry 3.23-stable
2026-03-13 08:28:39 <omni> algitbot: retry master
2026-03-13 08:28:47 <omni> algitbot: retry 3.23-stable
2026-03-13 08:28:50 <omni> algitbot: retry 3.22-stable
2026-03-13 08:28:53 <omni> algitbot: retry 3.21-stable
2026-03-13 08:28:57 <omni> algitbot: retry 3.20-stable
2026-03-13 14:47:07 <mio> algitbot: retry master
2026-03-14 04:05:12 <UnknownArtistBot> Hi all! check this out, An Unknown Artist - https://www.anunknownartist.com/
2026-03-14 08:12:56 <ikke> the stack trace for the panic goes into the stdlib fmt library..
2026-03-14 08:14:51 <ikke> https://tpaste.us/py0w?hl=true
2026-03-14 08:23:26 <ikke>                 // Should never happen, but we'll return a string here rather than
2026-03-14 08:23:28 <ikke>                 // crashing just in case it does.
2026-03-14 08:23:30 <ikke>                 return fmt.Sprintf("<invalid>.%s.%s", r.Type, r.Name)
2026-03-14 12:02:54 <omni> gummiboot was such a good name =(
2026-03-15 08:20:09 <ncopa> algitbot: retry master
2026-03-15 08:20:52 <ikke> ncopa: fyi, I was still doing some debugging on the rv64 builder
2026-03-15 08:21:01 <ncopa> ok, i figured
2026-03-15 08:21:36 <ncopa> I was trying to get build-edge-riscv64 forward but saw vim running so...
2026-03-15 08:23:26 <ikke> I've started the builder now
2026-03-15 13:39:21 <omni> nice
2026-03-16 13:56:40 <omni> nmeum: I think we either need to remove the cached distfiles or change to a temporary name for the guile source tarballs
2026-03-16 14:38:32 <omni> !99094
2026-03-16 14:46:10 <omni> algitbot: retry master
2026-03-16 22:10:48 <andypost[m]> algitbot: retry 3.23-stable
2026-03-16 22:28:35 <andypost[m]> algitbot: retry 3.23-stable
2026-03-16 22:43:13 <andypost[m]> algitbot: retry 3.23-stable
2026-03-16 22:50:07 <andypost[m]> algitbot: retry 3.23-stable
2026-03-16 23:19:20 <andypost[m]> algitbot: retry master
2026-03-17 09:47:20 <omni> duckdb on x86_64
2026-03-17 09:47:23 <omni> test/sql/storage/parallel/insert_order_preserving_odd_sized_batches.test_slow:73: FAILED:
2026-03-17 09:47:30 <omni> explicitly with message:
2026-03-17 09:47:37 <omni>   0
2026-03-17 09:59:41 <aelin> the sudo-rs fail on armv7 is super weird, that should not fail... unless /not/a/shell is a valid path on the machine
2026-03-17 10:01:56 <aelin> also passed CI on armv7 just fine in the MR, i have a feeling that the build environment is weird
2026-03-17 10:17:33 <omni> hmm... if rust continues to fail on x86_64, perhaps we should switch to the default thin-local lto there too...
2026-03-17 10:18:21 <omni> it didn't seem to have the issue in CI
2026-03-17 10:18:48 <omni> like this faf106afc16fa396862dd7a90d98dedf9858fb1d
2026-03-17 12:03:43 <omni> algitbot: retry master
2026-03-17 20:24:08 <aelin> ikke: is the armv7 builder stuck?
2026-03-17 20:25:16 <ikke> test system::tests::killpg_test has been running for over 60 seconds
2026-03-17 20:25:18 <ikke> yes
2026-03-17 20:29:31 <aelin> thank you!
2026-03-17 21:09:48 <omni> !96884
2026-03-18 14:14:19 <mio> algitbot: retry 3.22-stable
2026-03-18 15:06:51 <mio> objfw remote seems to be experiencing an ipv6 issue
2026-03-18 15:16:08 <mio> will wait for a copy of the source tarball to become available on 3.22 distfiles and retry
2026-03-18 15:18:02 <mio> or when ipv6 requests resolve again remotely, whichever happens first
2026-03-18 23:48:46 <omni> algitbot: retry 3.22-stable
2026-03-19 01:52:17 <mio> algitbot: retry 3.22-stable
2026-03-19 19:26:31 <ikke> algitbot: retry 3.22-stable
2026-03-19 22:19:34 <omni> fossdd: I cannot find MRs for the above, did you skip running the changes through CI before getting them in?
2026-03-19 22:25:58 <achill> ah damn it forgot i still had local commits
2026-03-19 22:28:23 <achill> i should just go to sleep lol
2026-03-20 06:12:12 <ikke> algitbot: retry mater
2026-03-20 06:12:14 <ikke> algitbot: retry master
2026-03-22 13:36:58 <achill> algitbot: retry master
2026-03-23 07:42:53 <omni> in case it is having OOM issues as in CI, there's !99457
2026-03-24 02:26:35 <lotheac> *facepalm*
2026-03-24 02:26:46 <lotheac> no such luck, eh
2026-03-24 02:31:38 <lotheac> https://github.com/ericwq/aprilsh/issues/96 asking the maintainer...
2026-03-24 12:54:46 <omni> OOM
2026-03-24 12:55:05 <omni> perhaps let the arm* builds complete and then retry?
2026-03-24 12:55:24 <omni> ..if they're on the same machine..
2026-03-24 15:12:52 <ikke> omni: aarch64 and *arm are on the same machine
2026-03-24 15:13:31 <ikke> But, in the last 24h, a minimum of >220G was available
2026-03-24 15:13:38 <ikke> so it's not just simple memory exhaustion
2026-03-24 15:14:04 <ikke> Something else must be going on
2026-03-24 15:14:55 <ikke> With available I mean that is has not been below 220G available at any time during builds
2026-03-24 15:16:27 <lotheac> is that based on sampling of "available" or is it a watermark metric
2026-03-24 15:17:11 <ikke> sampling
2026-03-24 15:17:25 <lotheac> could be something very quickly allocating 220G+ then :)
2026-03-24 15:17:34 <lotheac> (and dying before next sample)
2026-03-24 15:20:14 <ikke> But linux allows over committing, just allocating it should not cause issues
2026-03-24 15:20:15 <lotheac> although maybe that's a bit unlikely with overcommit, it would have to dirty all the memory to make it count
2026-03-24 15:20:16 <lotheac> yeah
2026-03-24 15:22:24 <ikke> Can it be some form of stack exhaustion?
2026-03-24 15:26:15 <lotheac> can't really be a "normal" allocation failure, if overcommit is enabled
2026-03-24 15:27:47 <ikke> cat /proc/sys/vm/overcommit_memory -> 0
2026-03-24 15:28:08 <lotheac> yeah, must be some other kind of memory resource then
2026-03-24 15:28:22 <ikke> address space unlikely on 64-bits
2026-03-24 15:28:38 <lotheac> indeed
2026-03-24 15:32:56 <lotheac> ulimits? just a guess, but -m -l -s -v seem relevant
2026-03-24 15:34:04 <ikke> -l) 8192
2026-03-24 15:34:06 <ikke> (-m) unlimited
2026-03-24 15:34:12 <ikke> (-s) 8192
2026-03-24 15:34:18 <ikke> (-v) unlimited
2026-03-24 16:19:33 <WhyNotHugo> Why does that one say my name instead of the package name O.o
2026-03-24 16:29:19 <ikke> WhyNotHugo: they decided to name a package after you
2026-03-24 16:39:57 <WhyNotHugo> ikke: If I ever write a static site generator, I'm gonna name it after the creator of hugo.
2026-03-24 22:05:55 <omni> algitbot: retry 3.23-stable
2026-03-25 16:19:33 <ikke> So now I do see a significant amount of memory used
2026-03-25 16:19:45 <ikke> At the lowest point, 23.5G available
2026-03-25 16:21:19 <lotheac> the thing that OOMed previously was rust though, right? so... apples/oranges?
2026-03-25 16:22:47 <ikke> That wasn't my point
2026-03-25 16:23:04 <lotheac> elaborate, please :)
2026-03-25 16:23:15 <ikke> Just that there is a clear difference in what I see with nodejs and rust
2026-03-25 16:23:28 <lotheac> right, right
2026-03-25 16:24:57 <lotheac> i think they're different in all respects -- rust uses llvm, nodejs failed with c++ (which i think would be gcc) / cc1plus -- and not even with a message relating to memory (rather "Terminated", so something SIGTERM'd it?)
2026-03-25 16:25:58 <ikke> I do have earlyoom running on that server
2026-03-25 16:26:28 <ikke> earlyoom: sending SIGTERM to process 48711 uid 1000 "cc1plus": oom_score 670
2026-03-25 16:27:01 <ikke> earlyoom: mem avail: 23732 of 238088 MiB ( 9.97%), swap free:    0 of 4095 MiB ( 0.00%)
2026-03-25 16:27:03 <ikke> earlyoom: low memory! at or below SIGTERM limits: mem 10.00%, swap 10.00%
2026-03-25 16:28:34 <ikke> Noteworthy is that that amount of memory available is also what zabbix measured :)
2026-03-25 16:37:06 <lotheac> ah, yeah, okay
2026-03-25 16:37:47 <lotheac> so that's definitive evidence that nodejs actually did get killed because of it's excessive memory usage, but we still don't know what's up with rust :)
2026-03-26 09:17:00 <omni> algitbot: retry 3.20-stable
2026-03-26 09:17:23 <omni> werd
2026-03-26 09:17:26 <omni> algitbot: retry 3.21-stable
2026-03-26 09:19:40 <omni> ikke: it's like they sometimes don't auto trigger?
2026-03-26 09:31:18 <omni> huh
2026-03-26 09:32:18 <omni> it built in CI
2026-03-26 09:33:35 <omni> algitbot: retry master
2026-03-26 16:36:25 <ikke> omni: again out of memory
2026-03-26 16:36:32 <omni> mhm
2026-03-26 16:36:36 <omni> algitbot: retry master
2026-03-26 16:36:46 <ikke> Would it be worth a try to increase stack size?
2026-03-26 16:37:18 <omni> idk, maybe?
2026-03-26 16:37:59 <omni> but that we're having OOM issues on s390x is probably because I switched lto from thin-local to thin, as it seemed to work
2026-03-26 16:38:32 <omni> I think it OOMed in CI when I patched it the other day, but didn't on build-edge-s390x
2026-03-26 16:38:35 <omni> this time it did
2026-03-26 16:39:15 <ikke> I'm mentioning it because I don't see any evidence that it's running out of RAM
2026-03-26 16:39:18 <ikke> in any if these cases
2026-03-26 16:47:44 <omni> I don't know, I only see the error messages in the logs
2026-03-26 16:47:54 <omni> rustc-LLVM ERROR: out of memory
2026-03-26 16:47:54 <omni> Buffer allocation failed
2026-03-26 16:47:54 <omni> rustc exited with signal: 6 (SIGABRT)
2026-03-26 16:47:54 <omni> error: could not compile `rustc_driver` (lib)
2026-03-26 16:48:17 <omni> and an alternative to lto thin-local seems to be to run with fewer concurrent jobs
2026-03-26 16:48:43 <ikke> omni: SIGABRT is the process itself aborting
2026-03-26 16:48:59 <ikke> So it received an error when trying to allocate memory
2026-03-26 16:49:20 <ikke> Due to overcommit, malloc should not return an error
2026-03-26 16:50:11 <omni> I have vague recollections of celie talking about this becoming an issue after some previous llvm upgrade, but I didn't keep up with all their insights
2026-03-26 16:50:58 <omni> if it continues to OOM on s390x, I've re-opened !99457
2026-03-26 16:52:05 <ikke> omni: I could try to build it a couple of times with an increased `ulimit -s`
2026-03-26 16:55:01 <lotheac> ikke: you could maybe run bpftrace to drill down on that ENOMEM hypothesis. doas bpftrace -e 'tracepoint:syscalls:sys_exit_* /args.ret == -12/ { printf("ENOMEM: %s %s(%s)\n", probe, comm, pid); }'
2026-03-26 16:55:25 <omni> ikke: if you want, I don't feel like I have the resources to solve it
2026-03-26 16:55:29 <omni> and there it went again
2026-03-26 16:56:06 <omni> if you give up, there's always !99457 and thin-local lto should be fine
2026-03-26 16:58:57 <omni> I mean, we used to build with lto thin-local on s390x before I changed it in the recent 1.94.0 upgrade
2026-03-26 17:01:56 <lotheac> ikke: also malloc (or mmap) does actually fail with ENOMEM if you ask for a stupid amount of memory even if overcommit=0 (eg. 2**55 bytes; i tested my above bpftrace program with that value and sure enough)
2026-03-26 22:43:39 <omni> ikke: or are you looking at it and paused the builder?
2026-03-26 22:43:56 <omni> (the merge didn't trigger the builder)
2026-03-27 06:16:13 <ikke> omni: yeah, I had the runner paused, but didn't see the failure yet
2026-03-27 09:16:31 <omni> ikke: I'll try to look at it next time there's a rust upgrade/rebuild
2026-03-28 00:14:59 <mio> algitbot: retry master
2026-03-28 00:24:13 <mio> algitbot: retry master
2026-03-28 00:59:13 <mio> algitbot: retry master
2026-03-28 01:07:57 <mio> algitbot: retry master
2026-03-28 01:29:22 <mio> algitbot: retry master
2026-03-28 02:26:17 <mio> algitbot: retry master
2026-03-28 05:53:50 <mio> algitbot: retry master
2026-03-28 07:54:28 <ikke> algitbot: retry master
2026-03-28 13:07:59 <mio> algitbot: retry master
2026-03-28 13:16:29 <mio> algitbot: retry master
2026-03-28 13:26:08 <mio> algitbot: retry master
2026-03-28 13:28:14 <mio> algitbot: retry master
2026-03-28 13:33:36 <mio> algitbot: retry master
2026-03-28 14:28:48 <mio> algitbot: retry master
2026-03-28 16:57:26 <mio> algitbot: retry master
2026-03-28 17:06:59 <mio> algitbot: retry master
2026-03-28 17:08:48 <mio> algitbot: retry master
2026-03-28 17:13:29 <mio> algitbot: retry master
2026-03-28 17:14:16 <mio> algitbot: retry master
2026-03-28 17:48:49 <mio> algitbot: retry master
2026-03-28 18:03:05 <mio> algitbot: retry master
2026-03-28 19:22:49 <mio> algitbot: retry master
2026-03-28 19:48:41 <mio> algitbot: retry master
2026-03-28 19:52:01 <mio> algitbot: retry master
2026-03-28 20:03:50 <mio> algitbot: retry master
2026-03-28 20:14:00 <mio> algitbot: retry master
2026-03-28 20:17:12 <mio> algitbot: retry master
2026-03-28 20:42:56 <mio> algitbot: retry master
2026-03-28 21:03:13 <mio> algitbot: retry master
2026-03-28 21:29:23 <mio> algitbot: retry master
2026-03-28 21:54:40 <mio> algitbot: retry master
2026-03-28 21:59:14 <mio> algitbot: retry master
2026-03-28 22:12:48 <mio> algitbot: retry master
2026-03-28 22:34:59 <mio> algitbot: retry master
2026-03-28 22:46:32 <mio> algitbot: retry master
2026-03-28 22:51:08 <mio> algitbot: retry master
2026-03-28 22:57:29 <mio> algitbot: retry master
2026-03-28 23:32:44 <mio> algitbot: retry master
2026-03-28 23:42:56 <mio> algitbot: retry master
2026-03-28 23:47:03 <mio> algitbot: retry master
2026-03-29 00:18:37 <mio> algitbot: retry master
2026-03-29 00:30:55 <mio> algitbot: retry master
2026-03-29 00:37:41 <mio> algitbot: retry master
2026-03-29 00:46:29 <mio> algitbot: retry master
2026-03-29 00:48:14 <mio> algitbot: retry master
2026-03-29 00:48:48 <mio> algitbot: retry master
2026-03-29 00:57:48 <mio> algitbot: retry master
2026-03-29 01:04:10 <mio> algitbot: retry master
2026-03-29 01:12:44 <mio> algitbot: retry master
2026-03-29 01:52:37 <mio> algitbot: retry master
2026-03-29 02:08:34 <mio> algitbot: retry master
2026-03-29 02:14:00 <mio> algitbot: retry master
2026-03-29 02:16:15 <mio> algitbot: retry master
2026-03-29 02:46:19 <mio> algitbot: retry master
2026-03-29 02:48:18 <mio> algitbot: retry master
2026-03-29 02:51:21 <mio> algitbot: retry master
2026-03-29 02:59:37 <mio> algitbot: retry master
2026-03-29 03:31:32 <mio> algitbot: retry master
2026-03-29 03:33:52 <mio> algitbot: retry master
2026-03-29 03:33:59 <mio> algitbot: retry master
2026-03-29 03:38:15 <mio> algitbot: retry master
2026-03-29 03:39:41 <mio> algitbot: retry master
2026-03-29 03:45:40 <mio> algitbot: retry master
2026-03-29 03:48:48 <mio> algitbot: retry master
2026-03-29 03:56:43 <mio> algitbot: retry master
2026-03-29 03:57:41 <mio> algitbot: retry master
2026-03-29 04:01:07 <mio> algitbot: retry master
2026-03-29 04:03:20 <mio> algitbot: retry master
2026-03-29 04:04:06 <mio> algitbot: retry master
2026-03-29 04:08:56 <mio> algitbot: retry master
2026-03-29 04:11:42 <mio> algitbot: retry master
2026-03-29 04:15:45 <mio> algitbot: retry master
2026-03-29 04:17:53 <mio> algitbot: retry master
2026-03-29 04:24:07 <mio> algitbot: retry master
2026-03-29 04:48:52 <mio> algitbot: retry master
2026-03-29 04:50:47 <mio> algitbot: retry master
2026-03-29 04:53:32 <mio> algitbot: retry master
2026-03-29 04:56:57 <mio> algitbot: retry master
2026-03-29 04:59:31 <mio> algitbot: retry master
2026-03-29 05:02:00 <mio> algitbot: retry master
2026-03-29 05:06:05 <mio> algitbot: retry master
2026-03-29 05:06:14 <mio> algitbot: retry master
2026-03-29 05:13:30 <mio> algitbot: retry master
2026-03-29 05:16:20 <mio> algitbot: retry master
2026-03-29 05:22:31 <mio> algitbot: retry master
2026-03-29 11:04:50 <achill> PRIVATE-TOKEN
2026-03-29 14:14:39 <mio> algitbot: retry master
2026-03-29 15:37:42 <mio> algitbot: retry master
2026-03-29 15:39:18 <mio> algitbot: retry master
2026-03-29 15:40:21 <mio> algitbot: retry master
2026-03-29 15:43:47 <mio> algitbot: retry master
2026-03-29 15:50:52 <mio> algitbot: retry master
2026-03-29 15:53:12 <mio> algitbot: retry master
2026-03-29 15:55:31 <mio> algitbot: retry master
2026-03-29 19:48:00 <ikke> algitbot: retry master
2026-03-29 20:06:36 <mio> algitbot: retry master
2026-03-29 20:07:13 <mio> algitbot: retry master
2026-03-29 20:19:45 <mio> algitbot: retry master
2026-03-30 00:07:28 <WhyNotHugo> jedi-language-server fixed in !99763
2026-03-30 00:10:40 <WhyNotHugo> Fix for py3-mpmath in !99761
2026-03-30 01:09:03 <omni> worked in ci, didn't it?
2026-03-30 06:04:35 <mio> algitbot: retry 3.23-stable
2026-03-30 06:48:40 <mio> maintainer notified in #18025
2026-03-30 06:49:44 <mio> algitbot: retry master
2026-03-30 06:56:57 <mio> algitbot: retry master
2026-03-30 07:04:04 <mio> algitbot: retry master
2026-03-30 07:06:51 <mio> algitbot: retry master
2026-03-30 07:14:36 <mio> algitbot: retry master
2026-03-30 07:18:54 <mio> algitbot: retry master
2026-03-30 07:20:01 <mio> algitbot: retry master
2026-03-30 07:24:41 <mio> algitbot: retry master
2026-03-30 10:22:51 <ikke> achill: checksum missing ^
2026-03-30 10:23:07 <achill> yeah
2026-03-30 10:23:08 <achill> -a57d60b10762f924bfdfe6409fed6647bb3d2ab6fd1bc22cbeeaad973b4b21e1b4b32bab8a786bdb198ded02b3f16255f1f60df05eb3c390aba401a423413d00  oh-my-zsh-0_git20250329.tar.gz
2026-03-30 10:23:08 <achill> +a57d60b10762f924bfdfe6409fed6647bb3d2ab6fd1bc22cbeeaad973b4b21e1b4b32bab8a786bdb198ded02b3f16255f1f60df05eb3c390aba401a423413d00  oh-my-zsh-0_git20260329.tar.gz
2026-03-30 10:23:11 <achill> lol these two look identical
2026-03-30 10:23:36 <achill> ah yeah the year lol
2026-03-30 12:37:26 <achill> okay why did you build in CI
2026-03-30 12:37:39 <achill> a
2026-03-30 15:11:31 <achill> algitbot: retry master
2026-03-30 17:54:28 <achill> algitbot: retry master
2026-03-30 21:42:18 <omni> algitbot: retry master
2026-03-31 19:10:47 <omni> huh, succeeded in CI
2026-03-31 19:11:08 <omni> I'll retry once armhf is done
2026-03-31 19:45:07 <omni> I wonder if it is somehow stuck on armhf
2026-03-31 19:46:44 <ikke> probably
2026-03-31 19:47:10 <ikke> algitbot: retry master
2026-03-31 21:13:56 <omni> hmm.. =/
2026-03-31 21:47:17 <omni> algitbot: retry master
2026-03-31 22:14:40 <omni> I've communicated a bit with upstream about it
2026-03-31 22:15:04 <omni> but I think it's weird
2026-03-31 22:15:50 <omni> !99894
2026-03-31 22:37:38 <omni> :o