2025-03-01 21:50:59 <mio> algitbot: retry 3.21-stable
2025-03-01 22:22:29 <mio> algitbot: retry 3.21-stable
2025-03-02 10:50:29 <nmeum> meh
2025-03-02 10:56:33 <nmeum> https://build.alpinelinux.org/buildlogs/build-edge-x86_64/main/fish/fish-4.0.0-r1.log
2025-03-02 10:56:42 <nmeum> > 125 - tmux-abbr.fish (Skipped)
2025-03-02 10:56:49 <nmeum> > 134 - tmux-multiline-prompt.fish (Skipped)
2025-03-02 10:56:49 <nmeum> ah lol
2025-03-02 10:56:57 <nmeum> these tests are skipped on the other arches
2025-03-02 10:58:24 <nmeum> ohhhhhhhhhhhhhhhhhhhh
2025-03-02 10:58:33 <nmeum> ikke: is tmux installed on the ppc64le builder for some reason?
2025-03-02 11:06:44 <nmeum> algitbot: retry master
2025-03-02 11:07:00 <nmeum> tadada, mystery solved
2025-03-02 11:40:10 <ikke> nmeum: thanks for figuring out
2025-03-02 11:40:34 <ikke> algitbot: retry master
2025-03-02 11:40:49 <nmeum> no problem, let's hope it works now :)
2025-03-02 11:47:25 <ikke> :)
2025-03-02 16:18:18 <mio> algitbot: retry master
2025-03-02 19:29:59 <fossdd[m]> J0WI if you read this, thanks for merging all these MRs! much appreciated
2025-03-02 20:06:55 <ikke> The stat for today is -31 MRs :)
2025-03-02 22:01:55 <omni> algitbot: retry master
2025-03-02 22:21:45 <omni> algitbot: retry master
2025-03-02 22:23:40 <omni> algitbot: retry master
2025-03-02 22:24:09 <omni> algitbot: retry master
2025-03-02 22:24:39 <omni> algitbot: retry master
2025-03-02 22:25:30 <omni> algitbot: retry master
2025-03-02 22:51:38 <mio> algitbot: retry master
2025-03-02 23:09:48 <omni> disable mkbrr tests on armv7 or disable completely?
2025-03-02 23:10:21 <omni> surprised it built on armhf but not armv7, isn't it usually the other way around?
2025-03-02 23:13:27 <fossdd[m]> im more surprised that it was sucessfull in ci
2025-03-03 00:05:11 <omni> should've included "on", but ok..
2025-03-03 01:32:48 <omni> =/
2025-03-04 00:43:25 <francis[m]> From Trusted and Vouched Dealers... (full message at <https://matrix.org/oftc/media/v1/media/download/AQefVRmNqzvMUASUle_DWZQGmTl870aTx3GwRSjgXAKaBILdG49X0AzyjZmPAqknNFCPJy8kM7p5-rIdSI9aT2pCeVprSO9AAG1hdHJpeC5vcmcvTHBma2Z2VlRqenFFdGdqSkRBaWZZZnZE>)
2025-03-04 00:52:16 <fossdd[m]> pj 😓
2025-03-04 22:13:32 <mio> algitbot: retry master
2025-03-04 22:16:59 <mio> algitbot: retry master
2025-03-04 22:45:29 <andypost[m]> algitbot: retry master
2025-03-06 12:26:21 <ptrc> i think i got it
2025-03-06 12:26:53 <ptrc> it used to link glib-2.0 and gobject-2.0 from gstreamer's `Requires:`
2025-03-06 12:27:04 <ptrc> but now they're in `Requires.private:` and meson doesn't pull them in
2025-03-06 12:27:15 <ptrc> or maybe they were in private all this time, but pkgconf picked them up somehow
2025-03-06 16:29:43 <mio> algitbot: retry master
2025-03-06 17:18:24 <mio> algitbot: retry master
2025-03-06 19:53:00 <mio> algitbot: retry master
2025-03-06 19:57:21 <mio> algitbot: retry master
2025-03-06 22:22:35 <ptrc> that was. well
2025-03-06 22:22:36 <ptrc> bad
2025-03-06 22:53:52 <mio> algitbot: retry master
2025-03-07 10:36:19 <fossdd[m]> algitbot: retry master
2025-03-07 14:56:31 <mio> algitbot: retry master
2025-03-07 15:05:36 <mio> ikke: thanks for merge!
2025-03-07 18:38:47 <ikke> Seems like chromium fails due argument incompattibility wrt pipewire
2025-03-07 19:22:01 <mio> algitbot: retry master
2025-03-07 23:25:34 <mio> algitbot: retry master
2025-03-07 23:27:04 <mio> something off with coreutils? `sha512sum: invalid option -- 'c'`
2025-03-07 23:28:53 <mio> ah, there is !81017
2025-03-08 13:43:59 <mio> algitbot: retry master
2025-03-08 13:48:52 <mio> algitbot: retry master
2025-03-08 16:00:22 <mio> algitbot: retry master
2025-03-08 23:23:56 <fossdd[m]> re pipewire: not sure if the best way is to disable the tests or disable it completley on riscv64
2025-03-08 23:24:22 <fossdd[m]> sigill sounds like a builder problem, but i dont know if the resulting binaries are affected or if they "just dont run" on the builder
2025-03-09 06:06:21 <Ariadne> algitbot: retry master
2025-03-09 15:45:17 <HRio> algitbot: retry master
2025-03-09 15:48:20 <HRio> algitbot: retry master
2025-03-09 17:49:55 <mio> algitbot: retry master
2025-03-09 19:53:41 <mio> algitbot: retry master
2025-03-09 21:42:20 <mio> algitbot: retry master
2025-03-10 13:34:04 <fossdd[m]> chromium failure: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/81083
2025-03-10 16:27:02 <ikke> ncopa: ^ error: implicit declaration of function 'annotate_reachable'
2025-03-10 16:31:23 <ikke> Probably caused by https://lore.kernel.org/all/20250305174506.868421566@linuxfoundation.org/
2025-03-10 16:32:58 <ncopa> whoops
2025-03-10 18:22:15 <fossdd[m]> loongarch64 linux-lts: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/81128
2025-03-10 19:11:32 <mio> algitbot: retry master
2025-03-10 21:30:32 <fossdd[m]> https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/81132 for electron
2025-03-10 21:33:14 <ikke> fossdd[m]: thanks
2025-03-10 23:29:27 <mio> algitbot: retry master
2025-03-11 00:51:37 <mio> algitbot: retry master
2025-03-11 12:43:03 <ikke> algitbot: retry 3.20-stable
2025-03-11 12:47:40 <ikke> algitbot: retry 3.18-stable
2025-03-12 14:40:55 <PureTryOut> algitbot: retry master
2025-03-12 15:36:25 <andypost[m]> algitbot: retry master
2025-03-12 16:15:56 <andypost[m]> algitbot: retry master
2025-03-13 03:12:00 <mio> algitbot: retry master
2025-03-13 03:17:49 <mio> algitbot: retry master
2025-03-13 06:14:07 <ikke> algitbot: retry master
2025-03-13 17:16:15 <ikke> algitbot: retry master
2025-03-13 22:13:50 <mio> algitbot: retry master
2025-03-14 03:31:50 <mio> algitbot: retry master
2025-03-14 04:12:36 <mio> ayakael: in case you're around ^
2025-03-14 15:43:25 <fossdd[m]> https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/81304 for ghostty
2025-03-14 15:43:45 <fossdd[m]> i hope itll actually fix it, zig is so confusing and the previous commit passed ci aswell
2025-03-14 16:21:32 <fossdd[m]> urgh apparently that was not the issue
2025-03-14 16:21:37 <ikke> :(
2025-03-14 16:21:59 <fossdd[m]> i love it when build systems dont actually tell the error message
2025-03-14 16:22:04 <fossdd[m]> only error: the following build command failed with exit code 1:
2025-03-14 16:22:15 <ikke> auch
2025-03-14 16:43:40 <ikke> algitbot: retry master
2025-03-14 16:45:28 <mio> is edge riscv64 still building php83-pecl-imagick-3.8.0_rc2-r0? it's been there for 8+ hours
2025-03-14 16:46:29 <mio> just wondering if still running or stuck
2025-03-14 16:50:48 <mio> algitbot: retry master
2025-03-14 16:51:02 <ikke> mio: I think I still see progress
2025-03-14 16:51:20 <ikke> But, 'TEST 78/337 [tests/073_Imagick_forwardFourierTransformImage_basic.phpt]' does not bode well
2025-03-14 16:51:38 <mio> ah, thanks
2025-03-14 16:52:13 <mio> a bit surprised it's taking longer than php83 itself might lol
2025-03-14 16:52:21 <ikke> yeah
2025-03-14 16:52:48 <ikke> That line seem to have appeared after I started tailing the log, but strace does seem to indicate a dead-lock
2025-03-14 16:53:15 <ikke> algitbot: retry master
2025-03-14 16:54:21 <mio> ouch
2025-03-15 00:46:16 <mio> algitbot: retry 3.21-stable
2025-03-15 01:23:21 <andypost[m]> algitbot: retry 3.19-stable
2025-03-15 02:24:00 <andypost[m]> algitbot: retry 3.21-stable
2025-03-15 07:25:23 <andypost[m]> algitbot: kick build-3-21-armv7
2025-03-16 03:12:14 <mio> algitbot: retry master
2025-03-16 03:41:24 <mio> algitbot: retry master
2025-03-16 04:23:48 <mio> algitbot: retry master
2025-03-16 11:51:14 <nmeum> algitbot: retry master
2025-03-16 13:04:18 <fossdd[m]> lego on 3.21: !81410
2025-03-16 14:24:59 <mio> algitbot: retry master
2025-03-16 14:32:56 <mio> algitbot: retry 3.21-stable
2025-03-16 14:35:46 <mio> algitbot: retry master
2025-03-16 14:37:08 <mio> algitbot: retry master
2025-03-16 14:43:37 <nmeum> puh, we need a better way to do rebuilds for statically linked software like go
2025-03-16 14:44:15 <mio> algitbot: retry master
2025-03-16 14:44:34 <mio> algitbot: retry master
2025-03-16 14:58:16 <mio> algitbot: retry master
2025-03-16 15:07:58 <mio> algitbot: retry master
2025-03-16 15:12:54 <mio> algitbot: retry master
2025-03-16 15:15:28 <mio> algitbot: retry master
2025-03-16 15:16:34 <mio> algitbot: retry master
2025-03-16 15:39:53 <mio> algitbot: retry master
2025-03-16 15:41:37 <mio> algitbot: retry master
2025-03-16 15:51:16 <mio> algitbot: retry master
2025-03-16 15:54:06 <mio> algitbot: retry master
2025-03-16 16:05:54 <mio> algitbot: retry master
2025-03-16 16:07:47 <mio> algitbot: retry master
2025-03-16 16:09:48 <mio> algitbot: retry master
2025-03-16 16:14:38 <mio> algitbot: retry master
2025-03-16 16:14:53 <mio> algitbot: retry master
2025-03-16 16:16:23 <mio> algitbot: retry master
2025-03-16 16:18:00 <mio> algitbot: retry master
2025-03-16 16:19:31 <mio> algitbot: retry master
2025-03-16 16:23:22 <mio> algitbot: retry master
2025-03-16 16:34:04 <mio> algitbot: retry master
2025-03-16 16:40:54 <mio> algitbot: retry master
2025-03-16 17:02:53 <ikke> new word, strgings
2025-03-16 17:06:34 <ikke> fun, tests relying on the internet not changing
2025-03-16 17:09:05 <mio> algitbot: retry master
2025-03-16 17:09:55 <mio> haha
2025-03-16 17:16:12 <fossdd[m]> ikke: hmm i think you still need to fix compat with go 1.23: !81420 !81410
2025-03-16 17:17:13 <mio> algitbot: retry master
2025-03-16 17:17:41 <mio> algitbot: retry master
2025-03-16 17:18:18 <ikke> fossdd[m]: but edge is 1.24?
2025-03-16 17:18:42 <ikke> fossdd[m]: and sorry for missing that MR
2025-03-16 17:21:39 <ikke> fossdd[m]: the build succeeded locally
2025-03-16 17:21:45 <fossdd[m]> uhm interesting
2025-03-16 17:22:06 <fossdd[m]> then nice i guess
2025-03-16 17:24:23 <mio> algitbot: retry master
2025-03-16 17:26:38 <mio> algitbot: retry master
2025-03-16 17:29:13 <ikke> fossdd[m]: I guess you are checking if tailscale 1.80.3 is fixing the test failure?
2025-03-16 17:29:45 <fossdd[m]> yes, but 1.80.3 had some other test failure aswell, i hope thats fixed now with the new go
2025-03-16 17:34:13 <mio> algitbot: retry master
2025-03-16 17:34:26 <mio> algitbot: retry master
2025-03-16 17:41:38 <andypost[m]> algitbot: retry master
2025-03-16 17:42:52 <andypost[m]> The build-3-21-armv7 builder hanging 2nd day on imagick, please kick it
2025-03-16 17:45:16 <andypost[m]> algitbot: retry 3.21-stable
2025-03-16 17:47:14 <fossdd[m]> !80797 fixes tailscale
2025-03-16 17:48:32 <mio> algitbot: retry master
2025-03-16 17:52:54 <fossdd[m]> no space left on device on build-edge-s390x
2025-03-16 17:54:30 <mio> yeah, there was a monitor notification in #-infra
2025-03-16 17:55:09 <mio> algitbot: retry master
2025-03-16 17:57:01 <mio> algitbot: retry master
2025-03-16 17:57:33 <andypost[m]> algitbot: retry 3.21-stable
2025-03-16 17:58:17 <mio> algitbot: retry master
2025-03-16 18:11:00 <mio> algitbot: retry master
2025-03-16 18:11:47 <mio> algitbot: retry master
2025-03-16 18:13:58 <mio> algitbot: retry 3.21-stable
2025-03-16 18:14:11 <mio> algitbot: retry master
2025-03-16 18:15:01 <mio> algitbot: retry master
2025-03-16 18:16:21 <mio> algitbot: retry master
2025-03-16 18:16:32 <mio> algitbot: retry master
2025-03-16 18:21:13 <mio> algitbot: retry master
2025-03-16 18:23:22 <mio> algitbot: retry 3.21-stable
2025-03-16 18:23:29 <mio> algitbot: retry master
2025-03-16 18:25:57 <mio> algitbot: retry master
2025-03-16 18:30:19 <mio> algitbot: retry master
2025-03-16 18:35:23 <andypost[m]> algitbot: retry 3.21-stable
2025-03-16 18:35:26 <mio> algitbot: retry master
2025-03-16 18:37:03 <mio> algitbot: retry master
2025-03-16 18:39:10 <mio> algitbot: retry 3.21-stable
2025-03-16 18:42:34 <mio> algitbot: retry 3.21-stable
2025-03-16 18:57:37 <mio> algitbot: retry master
2025-03-16 18:57:58 <mio> algitbot: retry 3.21-stable
2025-03-16 19:02:11 <mio> algitbot: retry master
2025-03-16 19:02:17 <mio> algitbot: retry 3.21-stable
2025-03-16 19:07:20 <mio> algitbot: retry master
2025-03-16 19:07:40 <mio> algitbot: retry 3.21-stable
2025-03-16 19:08:22 <mio> algitbot: retry master
2025-03-16 19:10:37 <mio> algitbot: retry master
2025-03-16 19:11:40 <mio> algitbot: retry master
2025-03-16 19:12:38 <mio> algitbot: retry master
2025-03-16 19:16:09 <mio> algitbot: retry 3.21-stable
2025-03-16 19:22:03 <mio> algitbot: retry master
2025-03-16 19:23:01 <mio> algitbot: retry master
2025-03-16 19:35:33 <mio> algitbot: retry master
2025-03-16 19:36:46 <mio> algitbot: retry master
2025-03-16 19:37:34 <mio> algitbot: retry master
2025-03-16 19:37:44 <mio> algitbot: retry master
2025-03-16 19:38:05 <mio> algitbot: retry master
2025-03-16 19:39:18 <mio> algitbot: retry master
2025-03-16 19:39:31 <mio> algitbot: retry master
2025-03-16 19:44:01 <ikke> algitbot: retry master
2025-03-16 19:50:18 <mio> algitbot: retry master
2025-03-16 19:50:39 <mio> algitbot: retry 3.21-stable
2025-03-16 19:51:35 <mio> algitbot: retry 3.21-stable
2025-03-16 19:52:54 <mio> algitbot: retry master
2025-03-16 19:55:51 <mio> algitbot: retry master
2025-03-16 19:56:11 <mio> algitbot: retry 3.21-stable
2025-03-16 19:57:44 <mio> algitbot: retry master
2025-03-16 20:02:57 <mio> algitbot: retry master
2025-03-16 20:08:43 <mio> algitbot: retry master
2025-03-16 20:08:54 <mio> algitbot: retry 3.21-stable
2025-03-16 20:11:56 <ikke> 75 merge requests merged today
2025-03-16 20:11:58 <ikke> so far
2025-03-16 20:18:44 <mio> good progress
2025-03-16 20:19:09 <mio> algitbot: retry master
2025-03-16 20:19:46 <mio> (also thanks for merge earlier)
2025-03-16 20:22:11 <mio> algitbot: retry 3.21-stable
2025-03-16 20:22:29 <mio> algitbot: retry master
2025-03-16 20:34:45 <mio> algitbot: retry 3.21-stable
2025-03-16 20:50:02 <mio> algitbot: retry master
2025-03-16 21:05:09 <mio> algitbot: retry master
2025-03-16 21:05:30 <mio> algitbot: retry 3.21-stable
2025-03-16 21:06:42 <mio> algitbot: retry master
2025-03-16 21:22:07 <mio> algitbot: retry master
2025-03-16 21:31:59 <mio> algitbot: retry master
2025-03-16 21:35:42 <mio> algitbot: retry master
2025-03-16 21:36:26 <mio> algitbot: retry master
2025-03-16 21:38:16 <mio> algitbot: retry master
2025-03-16 21:41:06 <mio> algitbot: retry master
2025-03-16 21:48:45 <mio> algitbot: retry master
2025-03-16 22:10:40 <mio> algitbot: retry master
2025-03-16 22:21:11 <mio> algitbot: retry master
2025-03-16 22:23:34 <mio> algitbot: retry master
2025-03-16 22:34:08 <mio> algitbot: retry master
2025-03-16 22:34:42 <mio> algitbot: retry 3.21-stable
2025-03-16 22:49:44 <mio> algitbot: retry 3.21-stable
2025-03-16 22:56:30 <fossdd[m]> !81435
2025-03-16 23:05:45 <mio> algitbot: retry master
2025-03-16 23:09:08 <mio> algitbot: retry master
2025-03-16 23:17:56 <mio> algitbot: retry master
2025-03-16 23:18:22 <mio> algitbot: retry 3.21-stable
2025-03-16 23:20:18 <mio> algitbot: retry master
2025-03-16 23:33:26 <mio> algitbot: retry master
2025-03-16 23:38:06 <mio> algitbot: retry master
2025-03-16 23:42:32 <mio> algitbot: retry master
2025-03-16 23:46:26 <mio> algitbot: retry master
2025-03-16 23:48:29 <mio> algitbot: retry master
2025-03-16 23:48:31 <mio> algitbot: retry 3.21-stable
2025-03-16 23:55:07 <mio> algitbot: retry master
2025-03-17 00:10:04 <mio> algitbot: retry master
2025-03-17 00:41:50 <mio> algitbot: retry 3.21-stable
2025-03-17 00:42:43 <mio> algitbot: retry 3.21-stable
2025-03-17 01:01:40 <mio> algitbot: retry 3.21-stable
2025-03-17 02:19:56 <mio> algitbot: retry master
2025-03-17 02:20:25 <mio> algitbot: retry 3.21-stable
2025-03-17 02:32:03 <mio> algitbot: retry 3.21-stable
2025-03-17 02:32:05 <mio> algitbot: retry master
2025-03-17 02:36:02 <mio> algitbot: retry master
2025-03-17 02:44:57 <mio> algitbot: retry master
2025-03-17 02:46:18 <mio> algitbot: retry master
2025-03-17 02:47:44 <mio> algitbot: retry master
2025-03-17 02:48:02 <mio> algitbot: retry master
2025-03-17 02:53:51 <mio> algitbot: retry master
2025-03-17 02:53:54 <mio> algitbot: retry 3.21-stable
2025-03-17 02:57:39 <mio> algitbot: retry master
2025-03-17 03:01:45 <mio> algitbot: retry master
2025-03-17 03:53:07 <mio> algitbot: retry master
2025-03-17 03:56:37 <mio> algitbot: retry master
2025-03-17 03:58:18 <mio> algitbot: retry master
2025-03-17 04:06:02 <mio> algitbot: retry master
2025-03-17 04:25:42 <mio> algitbot: retry master
2025-03-17 13:30:04 <mio> algitbot: retry master
2025-03-17 13:30:36 <mio> algitbot: retry master
2025-03-17 13:33:29 <mio> algitbot: retry master
2025-03-17 13:33:36 <mio> algitbot: retry master
2025-03-17 13:34:26 <mio> algitbot: retry master
2025-03-17 13:39:04 <mio> algitbot: retry master
2025-03-17 13:49:51 <mio> algitbot: retry master
2025-03-17 13:51:05 <mio> algitbot: retry master
2025-03-17 13:57:50 <mio> algitbot: retry master
2025-03-17 14:01:44 <mio> algitbot: retry master
2025-03-17 14:02:12 <mio> algitbot: retry master
2025-03-17 14:06:38 <mio> algitbot: retry master
2025-03-17 14:08:05 <mio> algitbot: retry master
2025-03-17 14:09:16 <mio> algitbot: retry master
2025-03-17 14:16:16 <mio> algitbot: retry master
2025-03-17 14:21:13 <mio> algitbot: retry master
2025-03-17 14:23:10 <mio> algitbot: retry master
2025-03-17 14:26:26 <mio> algitbot: retry master
2025-03-17 14:29:40 <mio> algitbot: retry master
2025-03-17 14:29:56 <mio> algitbot: retry master
2025-03-17 14:31:31 <mio> algitbot: retry master
2025-03-17 14:32:43 <mio> algitbot: retry master
2025-03-17 14:37:13 <mio> algitbot: retry master
2025-03-17 14:39:37 <mio> algitbot: retry master
2025-03-17 14:44:46 <mio> algitbot: retry master
2025-03-17 14:45:07 <mio> algitbot: retry master
2025-03-17 14:50:07 <mio> algitbot: retry master
2025-03-17 14:56:37 <mio> algitbot: retry master
2025-03-17 14:57:06 <mio> algitbot: retry master
2025-03-17 15:01:10 <mio> algitbot: retry master
2025-03-17 15:04:39 <mio> algitbot: retry master
2025-03-17 15:05:41 <mio> algitbot: retry master
2025-03-17 15:07:01 <mio> algitbot: retry master
2025-03-17 15:07:25 <mio> algitbot: retry master
2025-03-17 15:10:32 <mio> algitbot: retry master
2025-03-17 15:12:37 <mio> algitbot: retry master
2025-03-17 15:14:06 <mio> algitbot: retry master
2025-03-17 15:20:16 <mio> ncopa: ^
2025-03-17 15:20:43 <fossdd[m]> No space left on device
2025-03-17 15:20:45 <mio> ah, looks like just out of space
2025-03-17 15:20:47 <fossdd[m]> looks like a builder issue
2025-03-17 15:20:49 <fossdd[m]> yes
2025-03-17 15:21:23 <mio> okay. missed a notification in #-infra
2025-03-17 15:22:32 <mio> fossdd[m]: btw, not sure if this is something you might be interested in looking into https://build.alpinelinux.org/buildlogs/build-edge-aarch64/testing/ghostty/ghostty-1.1.2_git20250311-r0.log
2025-03-17 15:23:31 <mio> this came up earlier, saw you had backported a patch to build against zig 0.14.0
2025-03-17 15:24:49 <fossdd[m]> yeah i know, i it was part of the zig0.14 PR upstream, maybe just a pulling the latest commit would work
2025-03-17 15:25:03 <fossdd[m]> the worst is that the issue is only on the builder but not on ci
2025-03-17 15:26:40 <mio> okay, thanks. just mentioning in case it gets lost amid the other failed notifications
2025-03-17 15:26:59 <ncopa> mio: thanks for the ping
2025-03-17 15:27:11 <ncopa> I'll bring it up in #alpine-infra
2025-03-17 15:27:35 <mio> great, thanks
2025-03-17 15:41:00 <mio> algitbot: retry master
2025-03-17 15:42:37 <mio> algitbot: retry master
2025-03-17 15:43:22 <mio> algitbot: retry master
2025-03-17 15:58:07 <mio> algitbot: retry master
2025-03-17 16:05:36 <mio> algitbot: retry master
2025-03-17 16:10:21 <mio> algitbot: retry master
2025-03-17 16:11:34 <mio> algitbot: retry master
2025-03-17 16:12:18 <mio> algitbot: retry master
2025-03-17 16:13:51 <mio> algitbot: retry master
2025-03-17 16:33:20 <mio> algitbot: retry master
2025-03-17 16:36:33 <mio> algitbot: retry master
2025-03-17 16:39:02 <mio> algitbot: retry master
2025-03-17 16:42:27 <mio> algitbot: retry master
2025-03-17 16:42:50 <mio> algitbot: retry master
2025-03-17 16:45:15 <mio> algitbot: retry master
2025-03-17 16:46:57 <mio> algitbot: retry master
2025-03-17 16:53:11 <mio> algitbot: retry master
2025-03-17 16:57:07 <mio> algitbot: retry master
2025-03-17 17:00:50 <mio> algitbot: retry master
2025-03-17 17:04:17 <mio> algitbot: retry master
2025-03-17 17:04:38 <mio> algitbot: retry master
2025-03-17 17:08:47 <mio> algitbot: retry master
2025-03-17 17:12:10 <mio> algitbot: retry master
2025-03-17 17:18:34 <mio> algitbot: retry master
2025-03-17 17:23:16 <mio> algitbot: retry master
2025-03-17 17:25:59 <mio> algitbot: retry master
2025-03-17 17:26:36 <mio> algitbot: retry master
2025-03-17 17:30:40 <mio> algitbot: retry master
2025-03-17 17:31:08 <mio> algitbot: retry master
2025-03-17 17:31:37 <mio> algitbot: retry master
2025-03-17 17:34:06 <mio> algitbot: retry master
2025-03-17 17:36:02 <mio> algitbot: retry master
2025-03-17 17:38:44 <mio> algitbot: retry master
2025-03-17 17:40:19 <mio> algitbot: retry master
2025-03-17 17:47:22 <mio> algitbot: retry master
2025-03-17 17:49:05 <mio> algitbot: retry master
2025-03-17 17:50:38 <mio> algitbot: retry master
2025-03-17 17:50:44 <mio> algitbot: retry master
2025-03-17 17:51:28 <mio> algitbot: retry master
2025-03-17 17:52:59 <mio> algitbot: retry master
2025-03-17 17:53:13 <mio> algitbot: retry master
2025-03-17 17:55:54 <mio> algitbot: retry master
2025-03-17 17:57:38 <mio> algitbot: retry master
2025-03-17 17:58:17 <mio> algitbot: retry master
2025-03-17 18:03:25 <mio> algitbot: retry master
2025-03-17 18:09:57 <mio> algitbot: retry master
2025-03-17 18:11:28 <mio> algitbot: retry master
2025-03-17 18:13:47 <mio> algitbot: retry master
2025-03-17 18:16:56 <mio> algitbot: retry master
2025-03-17 18:22:38 <mio> algitbot: retry master
2025-03-17 18:31:39 <mio> algitbot: retry master
2025-03-17 18:35:10 <mio> algitbot: retry master
2025-03-17 18:37:06 <mio> algitbot: retry master
2025-03-17 18:40:36 <mio> algitbot: retry master
2025-03-17 18:41:06 <mio> algitbot: retry master
2025-03-17 18:41:58 <mio> algitbot: retry master
2025-03-17 18:42:37 <mio> algitbot: retry master
2025-03-17 18:48:41 <ikke> hugo apparently has brittle tests
2025-03-17 18:51:09 <mio> yeah, though hugo the issue seems to be loongarch-specific?
2025-03-17 18:51:38 <mio> there's an open MR for upgrade that also fails on CI for similar tests
2025-03-17 18:51:53 <mio> s/though hugo/though for hugo this time/
2025-03-17 18:52:44 <ikke> mio: the format related differences as well?
2025-03-17 18:53:24 <mio> algitbot: retry master
2025-03-17 18:53:38 <mio> think so? or were there additional test failures?
2025-03-17 18:53:52 <ikke> I've pasted one in the MR
2025-03-17 18:54:06 <ikke> differences appear to just be newlines
2025-03-17 18:55:18 <ikke> Most failures are just brittle tessts
2025-03-17 18:55:21 <ikke> utterly anoying
2025-03-17 18:56:09 <mio> yes
2025-03-17 18:57:07 <mio> https://gitlab.alpinelinux.org/hannes/aports/-/jobs/1745489#L1001
2025-03-17 18:57:28 <mio> yeah, s5cmd just passed on armv7 after multiple retries
2025-03-17 18:58:01 <mio> not entirely sure sometimes which ones just have flaky tests
2025-03-17 18:59:05 <andypost[m]> algitbot: retry master
2025-03-17 18:59:19 <ikke>         got:
2025-03-17 18:59:21 <ikke>           s"- pink.jpg"
2025-03-17 18:59:23 <ikke>         want:
2025-03-17 18:59:25 <ikke>           s"- pink.jpg"
2025-03-17 18:59:27 <ikke> I don't see the difference
2025-03-17 18:59:43 <mio> lol
2025-03-17 19:01:45 <mio> for miller, maintainer gave the okay to disable the specific tests for loongarch64 while loongarch folks look into a floating point issue that may be triggered it
2025-03-17 19:03:04 <mio> unfortunately can reproduce the oauth2-proxy test failure on x86_64
2025-03-17 19:03:20 <mio> still fails on upgrade to latest stable
2025-03-17 19:03:53 <mio> algitbot: retry master
2025-03-17 19:05:13 <mio> the remaining 5 on armv7 are all failed, mostly retrying to prebuild the remaining ones on other arches at this point
2025-03-17 19:06:28 <mio> algitbot: retry master
2025-03-17 19:06:57 <mio> algitbot: retry master
2025-03-17 19:08:59 <mio> algitbot: retry master
2025-03-17 19:13:53 <andypost[m]> algitbot: retry master
2025-03-17 19:16:22 <mio> algitbot: retry master
2025-03-17 19:21:32 <mio> algitbot: retry master
2025-03-17 19:28:55 <mio> algitbot: retry master
2025-03-17 20:26:11 <mio> algitbot: retry master
2025-03-17 20:27:01 <mio> algitbot: retry master
2025-03-17 21:03:05 <fossdd[m]> oh what is here for a minefield :/
2025-03-17 21:05:31 <mio> algitbot: retry master
2025-03-17 21:06:17 <mio> algitbot: retry master
2025-03-17 21:09:05 <ikke> fossdd[m]: ahuh
2025-03-17 21:23:52 <mio> algitbot: retry master
2025-03-17 21:42:13 <mio> algitbot: retry master
2025-03-17 21:57:39 <mio> algitbot: retry master
2025-03-17 22:06:04 <mio> algitbot: retry master
2025-03-17 22:06:20 <mio> algitbot: retry master
2025-03-17 22:37:35 <mio> algitbot: retry master
2025-03-17 22:54:19 <mio> algitbot: retry master
2025-03-17 22:56:10 <mio> algitbot: retry master
2025-03-17 22:56:31 <mio> algitbot: retry master
2025-03-17 22:59:59 <mio> algitbot: retry master
2025-03-17 23:02:54 <mio> algitbot: retry master
2025-03-17 23:06:08 <mio> algitbot: retry master
2025-03-17 23:28:38 <mio> algitbot: retry master
2025-03-17 23:29:55 <mio> algitbot: retry master
2025-03-17 23:30:54 <mio> algitbot: retry master
2025-03-17 23:41:37 <mio> algitbot: retry master
2025-03-17 23:44:11 <mio> algitbot: retry master
2025-03-17 23:45:46 <mio> algitbot: retry master
2025-03-17 23:59:22 <mio> algitbot: retry master
2025-03-18 00:13:32 <mio> algitbot: retry master
2025-03-18 00:20:01 <mio> algitbot: retry master
2025-03-18 01:00:30 <mio> algitbot: retry master
2025-03-18 01:07:05 <mio> algitbot: retry master
2025-03-18 01:23:27 <mio> algitbot: retry master
2025-03-18 01:29:06 <mio> algitbot: retry master
2025-03-18 01:31:41 <mio> algitbot: retry master
2025-03-18 01:38:58 <mio> algitbot: retry master
2025-03-18 02:04:04 <mio> algitbot: retry master
2025-03-18 02:35:30 <mio> algitbot: retry master
2025-03-18 03:27:26 <mio> algitbot: retry master
2025-03-18 03:33:07 <mio> algitbot: retry master
2025-03-18 03:39:23 <mio> algitbot: retry master
2025-03-18 03:47:42 <mio> algitbot: retry master
2025-03-18 04:34:43 <mio> algitbot: retry master
2025-03-18 04:52:22 <mio> algitbot: retry master
2025-03-18 04:55:57 <mio> algitbot: retry master
2025-03-18 05:03:54 <mio> algitbot: retry master
2025-03-18 05:07:23 <mio> algitbot: retry master
2025-03-18 05:11:36 <mio> algitbot: retry master
2025-03-18 05:35:08 <mio> algitbot: retry master
2025-03-18 05:37:58 <mio> algitbot: retry master
2025-03-18 05:45:52 <mio> algitbot: retry master
2025-03-18 05:48:35 <mio> algitbot: retry master
2025-03-18 05:59:21 <mio> algitbot: retry master
2025-03-18 06:07:15 <mio> algitbot: retry master
2025-03-18 06:09:15 <mio> algitbot: retry master
2025-03-18 09:14:30 <huajingyun1> algitbot: retry master
2025-03-18 12:10:49 <ikke> panic: test timed out after 1h0m0s
2025-03-18 12:10:51 <ikke> ouch
2025-03-18 13:14:49 <mio> algitbot: retry master
2025-03-18 13:16:58 <mio> algitbot: retry master
2025-03-18 13:26:35 <mio> algitbot: retry master
2025-03-18 13:30:45 <mio> algitbot: retry master
2025-03-18 13:35:22 <mio> algitbot: retry master
2025-03-18 13:35:56 <mio> algitbot: retry master
2025-03-18 14:25:01 <mio> algitbot: retry master
2025-03-18 14:32:26 <mio> algitbot: retry master
2025-03-18 14:35:50 <mio> algitbot: retry master
2025-03-18 14:45:34 <mio> algitbot: retry master
2025-03-18 14:46:18 <mio> algitbot: retry master
2025-03-18 14:52:01 <mio> algitbot: retry master
2025-03-18 14:54:17 <mio> algitbot: retry master
2025-03-18 15:19:53 <mio> algitbot: retry master
2025-03-18 15:26:34 <mio> algitbot: retry master
2025-03-18 15:54:05 <mio> Ariadne: would you by chance have a moment to look into ko? test failed across multiple arches
2025-03-18 17:05:10 <mio> algitbot: retry master
2025-03-18 18:18:41 <mio> algitbot: retry master
2025-03-18 22:14:08 <mio> algitbot: retry master
2025-03-19 05:59:14 <mio> algitbot: retry master
2025-03-19 06:01:42 <mio> algitbot: retry master
2025-03-19 06:04:13 <mio> algitbot: retry master
2025-03-19 06:04:37 <mio> algitbot: retry master
2025-03-19 06:05:57 <mio> algitbot: retry master
2025-03-19 06:48:56 <mio> algitbot: retry master
2025-03-19 07:21:40 <mio> algitbot: retry master
2025-03-19 07:22:26 <mio> algitbot: retry master
2025-03-19 07:22:52 <mio> algitbot: retry master
2025-03-19 07:23:31 <mio> algitbot: retry master
2025-03-19 07:25:08 <mio> algitbot: retry master
2025-03-19 07:25:50 <mio> algitbot: retry master
2025-03-19 07:27:29 <mio> algitbot: retry master
2025-03-19 07:30:49 <mio> algitbot: retry master
2025-03-19 07:37:22 <mio> algitbot: retry master
2025-03-19 11:51:20 <fossdd[m]> algitbot: retry master
2025-03-19 12:51:44 <mio> algitbot: retry master
2025-03-19 13:10:29 <mio> clock test ...?
2025-03-19 13:10:52 <mio> algitbot: retry master
2025-03-19 13:12:01 <mio> there we go
2025-03-19 13:15:28 <mio> there we go
2025-03-19 13:15:30 <mio> algitbot: retry master
2025-03-19 13:16:01 <mio> lol not that one
2025-03-19 13:25:40 <mio> algitbot: retry master
2025-03-19 13:27:50 <mio> algitbot: retry master
2025-03-19 13:28:24 <mio> algitbot: retry master
2025-03-19 13:29:57 <mio> algitbot: retry master
2025-03-19 13:31:00 <mio> algitbot: retry master
2025-03-19 14:46:49 <mio> algitbot: retry master
2025-03-19 14:57:12 <mio> algitbot: retry master
2025-03-19 14:59:34 <mio> algitbot: retry master
2025-03-19 15:09:12 <mio> algitbot: retry master
2025-03-19 15:16:48 <mio> algitbot: retry master
2025-03-19 15:29:33 <mio> algitbot: retry master
2025-03-19 15:33:33 <mio> algitbot: retry master
2025-03-19 17:34:00 <mio> algitbot: retry master
2025-03-19 17:34:42 <mio> algitbot: retry master
2025-03-19 17:38:29 <mio> algitbot: retry master
2025-03-19 18:07:50 <ikke> ugh, bad_alloc
2025-03-19 18:07:58 <ikke> algitbot: retry master
2025-03-19 18:37:01 <mio> algitbot: retry master
2025-03-19 18:41:12 <mio> algitbot: retry master
2025-03-19 19:03:01 <mio> algitbot: retry master
2025-03-19 19:10:11 <mio> algitbot: retry master
2025-03-19 19:24:50 <mio> algitbot: retry master
2025-03-19 19:26:12 <mio> algitbot: retry master
2025-03-19 19:39:07 <mio> algitbot: retry master
2025-03-19 19:42:17 <mio> algitbot: retry master
2025-03-19 20:12:13 <mio> algitbot: retry master
2025-03-19 20:33:05 <ikke> algitbot: retry master
2025-03-19 20:41:16 <mio> algitbot: retry master
2025-03-19 22:07:08 <mio> algitbot: retry master
2025-03-19 23:07:37 <mio> algitbot: retry master
2025-03-19 23:24:26 <mio> algitbot: retry master
2025-03-19 23:28:32 <mio> algitbot: retry master
2025-03-20 02:25:26 <mio> algitbot: retry master
2025-03-20 05:26:28 <mio> algitbot: retry master
2025-03-20 06:38:05 <ikke> algitbot: retry master
2025-03-20 13:25:44 <PureTryOut> algitbot: retry master
2025-03-20 14:10:54 <mio> algitbot: retry master
2025-03-20 14:17:02 <mio> algitbot: retry master
2025-03-20 15:09:50 <mio> algitbot: retry master
2025-03-20 15:10:56 <ikke> I saw a gh issue from Zig recommending throwing away ~/.cache/zig (for ghostty), but apparently that didn't help
2025-03-20 15:12:22 <mio> ah ... thanks for trying
2025-03-20 15:13:22 <mio> think the maintainer also tried to rm things in the cache as well in https://git.alpinelinux.org/aports/commit/testing/ghostty?id=8b9f56b016a3c2b364eec89d84207210d85cda48
2025-03-20 15:13:52 <mio> think it worked at the time, but something changed since maybe
2025-03-20 15:22:15 <ikke> Part of the problem is that there are not a lot of details of what is failing and why
2025-03-20 15:24:28 <mio> yeah
2025-03-20 15:26:59 <mio> looks like it already rebuilt on x86_64, is temporarily disabling it on aarch64 an option?
2025-03-20 15:27:27 <mio> to upload the rest of testing/
2025-03-20 17:30:09 <mio> algitbot: retry master
2025-03-20 17:51:26 <ikke> there's also a .zig-cache in $builddir, but that should get cleared each build
2025-03-20 18:09:39 <mio> okay ... maybe could see if !81651 will help
2025-03-20 18:10:25 <mio> algitbot: retry master
2025-03-20 18:13:28 <ikke> hmmm, maybe that helps
2025-03-20 18:25:30 <fossdd[m]> no it didn't :(
2025-03-20 18:25:34 <mio> aww
2025-03-20 18:25:36 <mio> algitbot: retry master
2025-03-20 18:25:36 <ikke> :(
2025-03-20 18:25:49 <ikke> fossdd[m]: but it did pass in CI?
2025-03-20 18:26:00 <fossdd[m]> yeah it apparently also di the last 2 times
2025-03-20 18:26:01 <fossdd[m]> why does zig have to do this to us
2025-03-20 18:26:12 <ikke> I mean, I already cleared ~/.cache/zig
2025-03-20 18:26:16 <ikke> not sure what else there can be
2025-03-20 18:26:37 <fossdd[m]> same
2025-03-20 18:54:53 <ikke> algitbot: retry master
2025-03-20 19:18:29 <mio> algitbot: retry master
2025-03-20 21:29:33 <mio> looking into sq, something flaky about the test
2025-03-21 00:10:10 <mio> algitbot: retry master
2025-03-21 01:38:44 <mio> algitbot: retry master
2025-03-21 02:31:36 <mio> algitbot: retry master
2025-03-22 14:47:45 <mio> algitbot: retry 3.21-stable
2025-03-23 16:39:25 <mio> algitbot: retry 3.21-stable
2025-03-23 21:18:44 <ptrc> algitbot: retry master
2025-03-23 21:18:48 <ptrc> algitbot: retry 3.21-stable
2025-03-23 21:18:49 <ptrc> whoops
2025-03-23 21:28:40 <ikke> #17010
2025-03-23 22:14:46 <mio> [FAIL] "before all" hook for "should show only collection matching the filter"
2025-03-23 22:14:47 <mio>       Timeout of 30000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves
2025-03-23 22:20:30 <mio> ayakael: you might have already seen the notification but just in case ^
2025-03-23 22:32:34 <mio> algitbot: retry 3.21-stable
2025-03-23 23:22:32 <mio> algitbot: retry master
2025-03-24 00:10:58 <mio> algitbot: retry master
2025-03-24 00:48:57 <mio> algitbot: retry master
2025-03-24 17:14:05 <mio> algitbot: retry master
2025-03-24 19:12:37 <ikke> (stopping the aarch64 builder to test something)(
2025-03-24 20:52:38 <mio> algitbot: retry 3.21-stable
2025-03-24 20:54:11 <mio> maintainer added !81862 for zotero tests
2025-03-24 21:44:46 <ikke> algitbot: retry 3.21-stable
2025-03-25 16:20:17 <ptrc> algitbot: retry master
2025-03-25 16:26:16 <ptrc> but also they're gone so
2025-03-25 16:26:19 <ptrc> gh
2025-03-25 16:26:31 <ptrc> wrong channel 
2025-03-25 16:26:34 <ptrc> algitbot: retry master
2025-03-25 16:43:07 <ptrc> algitbot: retry master
2025-03-25 17:14:21 <ptrc> algitbot: retry master
2025-03-25 17:26:34 <ptrc> algitbot: retry master
2025-03-25 17:34:57 <ptrc> algitbot: retry master
2025-03-27 12:55:20 <ikke> algitbot: retry master
2025-03-27 15:17:55 <mio> algitbot: retry master
2025-03-27 15:23:07 <mio> algitbot: retry master
2025-03-27 16:53:44 <ikke> dovecot: macros.h:173:21: error: size of unnamed array is negative
2025-03-27 16:53:50 <ikke> (affects 32-bits)
2025-03-27 19:20:56 <mio> algitbot: retry master
2025-03-27 19:30:01 <mio> algitbot: retry master
2025-03-27 19:51:37 <ptrc> algitbot: retry master
2025-03-27 19:51:49 <ptrc> the lld tests are flaky on x86, for some reason...
2025-03-27 19:52:23 <mio> algitbot: retry master
2025-03-27 19:54:01 <mio> algitbot: retry master
2025-03-27 20:43:40 <fossdd[m]> s390x wpewebkit: !82023
2025-03-27 20:43:54 <fossdd[m]> oh wait
2025-03-27 20:44:47 <fossdd[m]> algitbot: retry master
2025-03-27 20:46:08 <mio> think ptrc got to wpewebkit on s390x
2025-03-27 20:46:36 <mio> it may still fail on riscv64 and loongarch64, different issues
2025-03-27 20:47:02 <fossdd[m]> yeah it adds libjxl only to makedepends if its not on s390x
2025-03-27 20:47:05 <fossdd[m]> but... it does
2025-03-27 20:47:11 <fossdd[m]> uhhh
2025-03-27 20:49:57 <fossdd[m]> i think the tree was just out of date
2025-03-27 21:35:50 <andypost[m]> algitbot: retry master
2025-03-27 21:58:25 <mio> algitbot: retry master
2025-03-27 22:08:21 <mio> algitbot: retry master
2025-03-27 22:50:51 <mio> algitbot: retry master
2025-03-27 22:52:13 <mio> algitbot: retry master
2025-03-27 22:56:17 <mio> algitbot: retry master
2025-03-27 22:59:52 <mio> algitbot: retry master
2025-03-27 23:00:55 <mio> algitbot: retry master
2025-03-27 23:23:41 <andypost[m]> algitbot: retry master
2025-03-27 23:29:20 <andypost[m]> algitbot: retry master
2025-03-27 23:29:33 <mio> algitbot: retry master
2025-03-28 00:01:09 <andypost[m]> algitbot: retry master
2025-03-28 00:08:28 <andypost[m]> algitbot: retry master
2025-03-28 00:09:03 <andypost[m]> algitbot: retry master
2025-03-28 00:09:22 <andypost[m]> algitbot: retry master
2025-03-28 00:52:19 <mio> algitbot: retry master
2025-03-28 00:53:54 <mio> algitbot: retry master
2025-03-28 01:28:06 <mio> algitbot: retry master
2025-03-28 01:28:53 <mio> algitbot: retry master
2025-03-28 01:35:18 <mio> algitbot: retry master
2025-03-28 01:39:48 <mio> algitbot: retry master
2025-03-28 02:10:56 <mio> algitbot: retry master
2025-03-28 02:11:56 <mio> algitbot: retry master
2025-03-28 02:24:11 <mio> algitbot: retry master
2025-03-28 02:27:35 <mio> algitbot: retry master
2025-03-28 02:27:50 <mio> algitbot: retry master
2025-03-28 03:01:44 <mio> algitbot: retry master
2025-03-28 03:09:16 <mio> algitbot: retry master
2025-03-28 03:11:11 <mio> algitbot: retry master
2025-03-28 03:22:08 <mio> algitbot: retry master
2025-03-28 03:23:25 <mio> algitbot: retry master
2025-03-28 03:30:59 <mio> algitbot: retry master
2025-03-28 03:39:02 <mio> algitbot: retry master
2025-03-28 04:04:25 <mio> algitbot: retry master
2025-03-28 04:05:00 <mio> algitbot: retry master
2025-03-28 04:05:12 <mio> algitbot: retry master
2025-03-28 04:05:22 <mio> algitbot: retry master
2025-03-28 04:05:33 <mio> algitbot: retry master
2025-03-28 04:07:00 <mio> algitbot: retry master
2025-03-28 04:27:19 <mio> algitbot: retry master
2025-03-28 05:31:51 <mio> algitbot: retry master
2025-03-28 05:32:23 <mio> algitbot: retry master
2025-03-28 05:50:19 <mio> algitbot: retry master
2025-03-28 05:50:32 <mio> algitbot: retry master
2025-03-28 05:51:02 <mio> algitbot: retry master
2025-03-28 06:06:06 <mio> !82022 !82033 !82035 (the last two still waiting for ci to complete on 2-3 arches, but they're there in case they might be of help)
2025-03-28 06:14:33 <ikke> mio: thanks!
2025-03-28 06:17:07 <mio> you're welcome! there it goes
2025-03-28 06:17:50 <ikke> mio: ironically it means it will break community for those arches :P
2025-03-28 06:19:36 <mio> :(
2025-03-28 06:23:47 <mio> algitbot: retry master
2025-03-28 06:25:46 <mio> algitbot: retry master
2025-03-28 06:40:20 <mio> algitbot: retry master
2025-03-28 06:43:28 <mio> algitbot: retry master
2025-03-28 06:44:12 <ikke> huh, why did mbt fail on missing icu
2025-03-28 06:46:10 <mio> algitbot: retry master
2025-03-28 06:50:32 <mio> algitbot: retry master
2025-03-28 06:51:14 <mio> algitbot: retry master
2025-03-28 06:53:04 <mio> algitbot: retry master
2025-03-28 09:05:32 <ptrc> algitbot: retry master
2025-03-28 11:42:05 <andypost[m]> algitbot: retry master
2025-03-28 14:08:51 <andypost[m]> algitbot: retry master
2025-03-28 14:09:30 <andypost[m]> algitbot: retry master
2025-03-28 15:19:34 <mio> algitbot: retry master
2025-03-28 15:36:41 <mio> algitbot: retry master
2025-03-28 15:37:39 <mio> algitbot: retry master
2025-03-28 15:40:23 <mio> algitbot: retry master
2025-03-28 15:48:54 <mio> ncopa: could openfst be enabled on s390x and armhf as well? hfst is failing with the same issue there
2025-03-28 15:49:12 <ncopa> im testing s390x now
2025-03-28 15:49:21 <mio> great, thanks
2025-03-28 15:49:36 <ncopa> the CI machines have been busy all day
2025-03-28 15:49:43 <mio> yeah
2025-03-28 15:49:54 <ncopa> so im testing in my dev envs
2025-03-28 15:50:48 <mio> algitbot: retry master
2025-03-28 15:59:11 <mio> algitbot: retry master
2025-03-28 15:59:26 <mio> algitbot: retry master
2025-03-28 15:59:46 <mio> algitbot: retry master
2025-03-28 16:11:04 <mio> algitbot: retry master
2025-03-28 16:12:28 <mio> algitbot: retry master
2025-03-28 16:13:10 <mio> algitbot: retry master
2025-03-28 16:21:11 <mio> timblserver might need a rebuild against icu 76
2025-03-28 16:22:07 <mio> wonder if it was used on armv7, as it was able to build there
2025-03-28 16:22:47 <mio> s/as it was/as mbt was/
2025-03-28 16:26:28 <ncopa> timblserver didnt link to icu https://build.alpinelinux.org/buildlogs/build-edge-armv7/community/timblserver/timblserver-1.19-r0.log
2025-03-28 16:28:18 <mio> ah, icu-libs?
2025-03-28 16:28:49 <mio> historically timblserver was rebuilt against newer icu
2025-03-28 16:29:55 <ncopa> for some reason, the configure detects icu, the linkerflags are added, but library is not linked
2025-03-28 16:30:25 <ncopa> maybe its as-needed linker flag that makes it not link?
2025-03-28 16:31:11 <mio> possibly?
2025-03-28 16:31:53 <ncopa> dunno
2025-03-28 16:32:05 <mio> algitbot: retry master
2025-03-28 16:32:15 <ncopa> im working on zotero now. will build it with bundled icu
2025-03-28 16:32:22 <ncopa> like we did with firefox
2025-03-28 16:32:45 <ncopa> meh.. didnt work
2025-03-28 16:32:51 <ncopa> ok its weekend for me now
2025-03-28 16:33:10 <mio> still progress made, have a good weekend!
2025-03-28 16:33:18 <ncopa> you too!
2025-03-28 16:33:29 <mio> thanks :)
2025-03-28 16:33:45 <ncopa> maybe we should file an issue for zotero and ping the maintainer
2025-03-28 16:34:28 <mio> yes
2025-03-28 16:35:50 <mio> algitbot: retry master
2025-03-28 16:55:39 <ikke> algitbot: retry master
2025-03-28 17:20:08 <mio> algitbot: retry master
2025-03-28 17:40:24 <mio> algitbot: retry master
2025-03-28 17:57:03 <mio> algitbot: retry master
2025-03-28 18:09:45 <mio> algitbot: retry master
2025-03-28 18:22:01 <mio> algitbot: retry master
2025-03-28 18:25:04 <mio> algitbot: retry master
2025-03-28 18:58:23 <mio> algitbot: retry master
2025-03-28 19:02:20 <mio> algitbot: retry master
2025-03-28 19:21:16 <mio> algitbot: retry master
2025-03-28 19:44:44 <mio> algitbot: retry master
2025-03-28 19:46:39 <mio> algitbot: retry master
2025-03-28 20:08:30 <mio> algitbot: retry master
2025-03-28 20:16:22 <mio> algitbot: retry master
2025-03-28 20:22:01 <mio> algitbot: retry master
2025-03-28 20:25:20 <mio> algitbot: retry master
2025-03-28 20:44:08 <mio> algitbot: retry master
2025-03-28 20:46:32 <mio> algitbot: retry master
2025-03-28 21:05:40 <mio> algitbot: retry master
2025-03-28 21:07:48 <mio> algitbot: retry master
2025-03-28 21:10:07 <mio> algitbot: retry master
2025-03-28 21:29:08 <mio> algitbot: retry master
2025-03-28 21:54:45 <mio> algitbot: retry master
2025-03-28 21:58:17 <mio> algitbot: retry master
2025-03-28 22:10:27 <mio> algitbot: retry master
2025-03-28 22:25:21 <mio> algitbot: retry master
2025-03-28 22:56:13 <mio> algitbot: retry master
2025-03-28 23:01:05 <mio> algitbot: retry master
2025-03-28 23:15:16 <mio> algitbot: retry master
2025-03-28 23:31:06 <mio> algitbot: retry master
2025-03-29 00:18:57 <mio> algitbot: retry master
2025-03-29 01:07:15 <mio> algitbot: retry master
2025-03-29 02:21:19 <mio> algitbot: retry master
2025-03-29 03:35:15 <mio> algitbot: retry master
2025-03-29 03:38:02 <mio> algitbot: retry master
2025-03-29 04:28:05 <mio> algitbot: retry master
2025-03-29 04:44:26 <mio> algitbot: retry master
2025-03-29 04:50:28 <mio> algitbot: retry master
2025-03-29 04:59:42 <mio> algitbot: retry master
2025-03-29 05:39:24 <mio> algitbot: retry master
2025-03-29 05:58:52 <mio> zotero has a potential fix, waiting to hear from zotero maintainer whether they can potentially incorporate it with their existing upgrade MR to avoid rebuilding twice on the builders
2025-03-29 06:04:08 <mio> (left a comment on the open MR)
2025-03-29 06:06:36 <mio> wpewebkit also failed on riscv64 ci last checked, but riscv64 ci has been busy, haven't looked into it
2025-03-29 12:35:17 <andypost[m]> algitbot: retry master
2025-03-29 13:19:39 <mio> algitbot: retry master
2025-03-29 13:22:49 <mio> algitbot: retry master
2025-03-29 13:43:40 <mio> algitbot: retry master
2025-03-29 14:05:04 <mio> algitbot: retry master
2025-03-29 14:23:03 <mio> algitbot: retry master
2025-03-29 14:26:33 <mio> algitbot: retry master
2025-03-29 14:31:57 <mio> algitbot: retry master
2025-03-29 14:34:52 <mio> algitbot: retry master
2025-03-29 14:37:16 <mio> algitbot: retry master
2025-03-29 14:40:37 <mio> algitbot: retry master
2025-03-29 14:43:55 <mio> algitbot: retry master
2025-03-29 14:45:13 <mio> ikke: !81782 should be ready to go
2025-03-29 14:45:51 <mio> algitbot: retry master
2025-03-29 14:46:09 <ikke> mio: right, was keeping an eye on it
2025-03-29 14:46:15 <mio> thanks :)
2025-03-29 14:57:16 <mio> algitbot: retry master
2025-03-29 14:59:41 <mio> algitbot: retry master
2025-03-29 15:06:59 <mio> algitbot: retry master
2025-03-29 15:21:43 <mio> algitbot: retry master
2025-03-29 16:03:58 <mio> algitbot: retry master
2025-03-29 16:35:25 <mio> algitbot: retry master
2025-03-29 16:36:06 <mio> algitbot: retry master
2025-03-29 16:36:18 <mio> algitbot: retry master
2025-03-29 16:36:39 <mio> algitbot: retry master
2025-03-29 16:36:51 <mio> algitbot: retry master
2025-03-29 16:55:44 <mio> algitbot: retry master
2025-03-29 16:57:40 <mio> algitbot: retry master
2025-03-29 17:02:14 <mio> dart seems to be having trouble self-bootstrapping without older icu
2025-03-29 17:02:42 <mio> (or temporary access to older icu?)
2025-03-29 17:07:27 <ikke> hmm, that's anoying
2025-03-29 17:11:54 <ikke> mio: the problem is that if we have icu-74 available, it will also build the next dart against that
2025-03-29 17:15:56 <mio> yeah ... wonder if there is a way to have both the bootstrap and dart use a "vendored" version then split it up again afterwards
2025-03-29 17:16:12 <mio> to use system version again
2025-03-29 17:16:49 <ikke> there is a patch to devendor, so I suppose not applying that patch would result in vendored icu to be used?
2025-03-29 17:18:01 <mio> possibly
2025-03-29 17:20:13 <ikke> I think we had similar issues with haskell before with libffi
2025-03-29 17:22:06 <mio> how was it resolved?
2025-03-29 17:22:19 <ikke> If I recall, in a similar fashion
2025-03-29 17:22:55 <mio> ah okay
2025-03-29 17:24:49 <ikke> testing it in my build container now
2025-03-29 17:25:29 <mio> thanks for looking into it :)
2025-03-29 17:26:29 <ikke> It's not going great so far
2025-03-29 17:26:40 <ikke> ninja: file is missing and not created by any action: '../../flutter/third_party/icu/flutter/icudtl.dat'
2025-03-29 17:27:33 <ikke> it's being removed in prepare
2025-03-29 17:29:50 <ikke> Now it's at least building
2025-03-29 17:33:28 <ikke> maybe we need a separate bootstrap version that has bundled dependencies
2025-03-29 17:37:19 <mio> there's a dart-stage0? looks like it has lower priority
2025-03-29 17:38:16 <ikke> oh
2025-03-29 17:39:01 <mio> not sure if it will help in this, maybe maintainer input would be good if they went to trouble to unbundle
2025-03-29 17:39:07 <ikke> yes, absolutely
2025-03-29 17:39:16 <ikke> stage0 is only used in absence of the main package
2025-03-29 17:39:36 <ikke> but that's a simpler solution if that builds
2025-03-29 17:39:54 <ikke> Then I just need to make sure that's installed
2025-03-29 17:40:36 <ikke> checksum failure
2025-03-29 17:50:43 <mio> aww
2025-03-29 17:59:21 <ikke> testing building on armv7 with stage0 now
2025-03-29 18:04:08 <mio> okay!
2025-03-29 18:06:19 <ikke> built dart with -stage0, going to build it with -bootstrap now
2025-03-29 18:06:35 <ikke> Not sure if it will matter a lot
2025-03-29 18:26:20 <mio> algitbot: retry master
2025-03-29 18:31:36 <mio> algitbot: retry master
2025-03-29 18:32:54 <ikke> ok, armv7 is finished
2025-03-29 18:33:12 <ikke> https://tpaste.us/RoMY 
2025-03-29 18:33:16 <ikke> looks good?
2025-03-29 18:39:16 <mio> cool, looks like it worked?
2025-03-29 18:39:25 <ikke> yes
2025-03-29 18:40:11 <ikke> 2 more arches to go
2025-03-29 18:40:18 <mio> :)
2025-03-29 18:40:27 <ikke> \o/
2025-03-29 18:40:55 <mio> \o/
2025-03-29 18:41:25 <ikke> once x86_64 or aarch64 fails, I'll work on those
2025-03-29 18:41:43 <mio> okay, thanks :)
2025-03-29 19:26:55 <mio> ikke: dart on aarch64 starting/in progress?
2025-03-29 19:28:33 <ikke> working on it now
2025-03-29 19:28:47 <mio> okay!
2025-03-29 19:29:14 <ikke> building with -stage0
2025-03-29 19:35:31 <ikke> building with -bootstrap
2025-03-29 19:40:18 <ikke> done
2025-03-29 19:40:38 <ikke> right on time
2025-03-29 19:41:33 <ikke> building with stage0
2025-03-29 19:53:44 <ikke> building with bootstrap
2025-03-29 20:09:16 <ikke> Done as well :)
2025-03-29 20:09:29 <ikke> mio: thanks for pointing out stage0.
2025-03-29 20:11:12 <mio> great, thanks!
2025-03-29 20:11:51 <mio> you're welcome, just exchanging ideas to resolve the error
2025-03-29 20:14:55 <ikke> Yes, absolutely
2025-03-29 20:15:03 <ikke> collaboration :)
2025-03-29 20:16:01 <mio> :)
2025-03-29 20:18:12 <mio> is ceph18 still progressing on the riscv64 builder? it was a busy day for riscv64 ci, not sure if it's just working its way through the build, over 12h
2025-03-29 20:18:32 <ikke> the builder is awol atm
2025-03-29 20:18:38 <ikke> carlo will check on monday
2025-03-29 20:18:46 <mio> ah okay, thanks
2025-03-29 20:29:32 <ikke> hmm, we could disable deno, let the builder upload, then enable it again
2025-03-29 20:29:55 <ikke> It's broken anyway
2025-03-29 20:32:31 <mio> yeah
2025-03-29 20:33:41 <mio> 4 patches to be realigned if upgrading, don't know yet whether it would fix the tests
2025-03-29 20:34:46 <mio> realigned/refreshed ... big if
2025-03-29 20:43:20 <ikke> algitbot: retry master
2025-03-29 20:45:03 <ikke> algitbot: retry master
2025-03-29 20:45:23 <ikke> 🤐
2025-03-29 20:58:20 <mio> \o/
2025-03-29 21:12:49 <mio> algitbot: retry master
2025-03-29 21:13:24 <mio> ah ... electron
2025-03-29 21:13:44 <ikke> yeah
2025-03-29 21:13:49 <ikke> it's not in the list of rebuilds
2025-03-29 21:16:29 <ikke> needs to be bumped
2025-03-29 21:17:10 <mio> yes ... wonder if there is still an issue with electron rebuild
2025-03-29 21:17:21 <ikke> We'll find out..
2025-03-29 21:18:06 <mio> accidentally sent aarch64 back to community/, sorry
2025-03-29 21:18:48 <ikke> well, it was bound to happen
2025-03-29 21:19:13 <ikke> But my goal was at least to have community uploaded
2025-03-29 21:21:09 <mio> yeah
2025-03-29 22:03:13 <mio> ikke: do you still want to try electron rebuild on aarch64, or should aarch64 be left in community/ for now?
2025-03-29 22:03:31 <mio> since deno just exited
2025-03-29 22:03:32 <ikke> I can try it
2025-03-29 22:03:54 <ikke> algitbot: retry master
2025-03-29 23:09:27 <mio> libs may need a rebuild against newer libxml2
2025-03-30 00:35:24 <ptrc> sigh.
2025-03-30 00:36:03 <mio> are you okay?
2025-03-30 00:36:24 <mio> or, how are things going?
2025-03-30 00:37:16 <mio> not sure if would be any help, but will be around a little bit, if only to cheer on the effort
2025-03-30 00:49:30 <mio> s/are things/is the rebuild/
2025-03-30 00:53:19 <ptrc> for now, i hope the libxml2.13 package will get picked up by the builders once everything else ( e.g. all llvm/clang versions ) is done
2025-03-30 00:53:37 <ptrc> and that should sustain existing systems, as long as nothing links against both of them
2025-03-30 00:53:48 <ptrc> chromium is gonna be a pain in the ass, i'm pretty sure
2025-03-30 00:56:07 <mio> great, thanks ... ouch on chromium
2025-03-30 00:57:34 <mio> algitbot: retry master
2025-03-30 00:57:48 <mio> algitbot: retry master
2025-03-30 00:58:13 <ptrc> ah. that's not good... i got the same errors a while ago when testing rootbld but i assumed those were because of rootbld
2025-03-30 01:02:21 <mio> algitbot: retry master
2025-03-30 01:03:14 <mio> there were a few functions removed in the new version, don't know if related
2025-03-30 01:03:40 <mio> according to the changelog
2025-03-30 01:03:54 <mio> libxml2 that is
2025-03-30 01:08:48 <mio> algitbot: retry master
2025-03-30 01:09:16 <mio> algitbot: retry master
2025-03-30 01:12:47 <ptrc> yeah no
2025-03-30 01:12:48 <ptrc> sigh
2025-03-30 01:24:26 <mio> algitbot: retry master
2025-03-30 01:24:51 <ptrc> afaict the gettext failures are not related to the libxml2 upgrade
2025-03-30 01:25:00 <ptrc> i've looked at my logs and they're the exact same tests
2025-03-30 01:28:38 <mio> okay. last rebuilt successfully Wed, 27 Mar 2024 17:39:20 +0000, -r0
2025-03-30 01:29:51 <mio> that might not be right
2025-03-30 01:30:32 <ptrc> what, gettext?
2025-03-30 01:30:52 <mio> https://git.alpinelinux.org/aports/log/main/gettext
2025-03-30 01:31:04 <ptrc> yeah that does sound about right
2025-03-30 01:31:13 <ptrc> we are also two versions behind
2025-03-30 01:31:26 <mio> ah okay
2025-03-30 01:33:55 <mio> is the plan to upgrade around release time?
2025-03-30 01:42:20 <mio> algitbot: retry master
2025-03-30 01:45:59 <mio> algitbot: retry master
2025-03-30 02:03:36 <mio> algitbot: retry master
2025-03-30 02:16:08 <mio> algitbot: retry master
2025-03-30 02:24:54 <mio> algitbot: retry master
2025-03-30 02:30:15 <mio> algitbot: retry master
2025-03-30 02:32:38 <mio> algitbot: retry master
2025-03-30 02:52:19 <mio> algitbot: retry master
2025-03-30 02:57:11 <mio> algitbot: retry master
2025-03-30 02:58:53 <mio> algitbot: retry master
2025-03-30 03:01:42 <mio> algitbot: retry master
2025-03-30 03:10:24 <mio> algitbot: retry master
2025-03-30 03:22:34 <mio> algitbot: retry master
2025-03-30 04:23:18 <mio> gettext failed tests are likely due to libunistring 1.3 https://savannah.gnu.org/bugs/?66502 apparently fixed in >= 0.23 (there is an existing draft MR for a 0.24 upgrade)
2025-03-30 04:25:25 <mio> ikke: for electron, maintainer has been notified and is working on it, as it's also needed for a signal-desktop upgrade MR
2025-03-30 05:28:39 <ikke> algitbot: retry master
2025-03-30 05:43:35 <ikke> mio: removing older versions of libxml2 does not fix gettext
2025-03-30 05:43:53 <ikke> (older -> not current version in APKBUILD)
2025-03-30 08:54:55 <ikke> #17035
2025-03-30 10:32:23 <ikke> This is a mess
2025-03-30 12:50:34 <mio> ikke: you're right, it's won't fix gettext specifically, but the other packages queued up on the builder would still pull the newer libxml2
2025-03-30 12:51:17 <mio> including gettext, and think there is another bug report filed in gettext bug tracker about building with libxml2
2025-03-30 12:52:08 <mio> 2.14.0 that is, so it likely will have some issue if it too pulls the newer version
2025-03-30 12:53:59 <ikke> Working on !80902
2025-03-30 12:54:19 <ikke> which also forces libxml2 2.13
2025-03-30 12:54:36 <mio> https://savannah.gnu.org/bugs/?66960 bug #66960: gettext-0.24 test failures with libxml-2.14.0
2025-03-30 12:54:38 <ikke> It fails on armhf
2025-03-30 12:54:46 <ikke> yes, I've found that one
2025-03-30 12:55:18 <mio> yeah, was looking at the draft MR
2025-03-30 12:57:12 <mio> ah, meant the older draft MR, thanks for newer one
2025-03-30 12:57:46 <ikke> I tried to update to 0.23.1 as an intermediate to see if that would avoid some newer test failures
2025-03-30 12:59:09 <ikke> https://tpaste.us/nNd4 
2025-03-30 12:59:52 <ikke> It's anoying that the test suite only writes details to files
2025-03-30 13:01:06 <mio> is it possible to try with downgraded libunistring?
2025-03-30 13:01:44 <mio> not sure if that was the trigger for the other arches' test failures
2025-03-30 13:02:19 <ikke> gettext 2.13 fixed the libunistring issues
2025-03-30 13:02:34 <mio> the 0.23 apparently
2025-03-30 13:02:44 <ikke> sorry, yes
2025-03-30 13:06:08 <mio> guess there are two items at the moment, clearing the remaining queued up builds from the libxml2 change, and gettext
2025-03-30 13:06:39 <mio> is gettext required by the other builds?
2025-03-30 13:08:25 <ikke> https://tpaste.us/zPEZ 
2025-03-30 13:09:45 <ikke> cannot find anything regarding the memset_explicit test
2025-03-30 13:10:21 <mio> what if ... temporarily skipping the test to get the rest of the gettext dependents through the build queue?
2025-03-30 13:11:06 <ikke> This does sound like a serious test failure, not sure if we should ignore it
2025-03-30 13:14:23 <mio> yeah, it should still be fixed in the end. there's no urgency to restore the older state of packages on the cdn?
2025-03-30 13:20:34 <ikke> Was hoping we could fix it by upgrading it, but I suppose that'll have to wait
2025-03-30 13:22:40 <mio> yeah
2025-03-30 13:28:32 <ikke> how to disable the test without autoconf complaining
2025-03-30 13:31:36 <mio> does something like this work? https://git.alpinelinux.org/aports/tree/main/gettext/skip-tests-musl.patch
2025-03-30 13:31:45 <mio> "exit 77"
2025-03-30 13:32:13 <ikke> let me try
2025-03-30 14:14:10 <ikke> hmm, strange, getting 8 new test errors locally :/
2025-03-30 14:23:34 <mio> odd
2025-03-30 14:24:36 <ikke> verifying on the builder
2025-03-30 14:24:38 <mio> trying 0.23 on ci, probably won't make much difference, at least to get test results
2025-03-30 14:24:59 <ikke> mio: did you see my changes to include test-suite.log files in artifacts?
2025-03-30 14:25:21 <mio> no, that would be very useful, thanks!
2025-03-30 14:25:37 <ikke> It's in the 0.24.0 upgrade MR
2025-03-30 14:25:51 <mio> was trying to primitively cat them to stdout
2025-03-30 14:26:29 <mio> thanks, will take a look
2025-03-30 14:31:00 <ikke> Also failing on the build :/
2025-03-30 14:32:09 <ikke> So now what
2025-03-30 14:36:24 <ikke> I feel like pushing the 0.24 upgrade and fix armhf later
2025-03-30 14:38:12 <mio> yeah, maybe xfail/skip the test on armhf for now
2025-03-30 14:38:53 <ikke> test_heap: address range is still mapped after free().
2025-03-30 14:38:55 <ikke> test-memset_explicit.c:243: assertion 'count < 50' failed
2025-03-30 14:38:59 <ikke> Not sure if we should skip a text like this
2025-03-30 14:40:11 <mio> yes, sorry wasn't clear, xfail to fix later
2025-03-30 14:40:22 <ikke> isn't xfail the same as skipping?
2025-03-30 14:40:39 <mio> skipping would not run the test, xfail lets it fail but it doesn't error out
2025-03-30 14:40:58 <mio> if it were to fail
2025-03-30 14:41:55 <ikke> In both cases it could lead to a broken package to be published
2025-03-30 14:44:39 <mio> if pushing 0.24, you meant disable on armhf?
2025-03-30 14:44:56 <mio> but then the dependents would need to be disabled as well, or ...?
2025-03-30 14:45:29 <ikke> Not disabling on armhf, just let it fail
2025-03-30 14:45:41 <mio> ah okay
2025-03-30 14:46:17 <mio> yeah, in that case it should help clear the other arches first
2025-03-30 14:47:05 <ikke> mio: that was my idea
2025-03-30 14:47:15 <ikke> not ideal, but I think our best option for now
2025-03-30 14:47:17 <mio> yes :)
2025-03-30 14:47:41 <mio> acknowledging it's your idea :)
2025-03-30 14:48:32 <mio> yeah. the sooner cdn state is restored, maybe less ripple effects
2025-03-30 14:53:38 <ikke> mio: can you review !80902?
2025-03-30 14:57:29 <mio> looks okay?
2025-03-30 14:58:04 <mio> algitbot: retry master
2025-03-30 14:58:19 <mio> algitbot: retry master
2025-03-30 14:58:29 <ptrc> sigh... caught up to everything; sorry for following up the botched upgrade with the rebuilds, and thanks to you both for fixing up my mistakes
2025-03-30 14:58:55 <ptrc> also, any chance we could add libxml2-dev~1.13 to the world on builders?
2025-03-30 14:59:04 <ptrc> 2.13*
2025-03-30 14:59:32 <ikke> I've at least added it to gettext makedepnds
2025-03-30 14:59:36 <ptrc> because currently there's only a handful of packages that link against the new version, but it seems like it's still getting picked up by other stuff
2025-03-30 14:59:49 <mio> algitbot: retry master
2025-03-30 15:01:39 <ikke> algitbot: retry master
2025-03-30 15:01:52 <mio> algitbot: retry master
2025-03-30 15:02:39 <mio> ptrc: no worries
2025-03-30 15:03:27 <mio> ikke: maybe will wait for libxml2-dev~2.13 add to world before my retrying on builders again?
2025-03-30 15:03:38 <mio> in case they pick something else besides gettext to build
2025-03-30 15:03:42 <ikke> I'm not adding it just yet
2025-03-30 15:03:48 <ikke> Want to avoid it if possible
2025-03-30 15:04:39 <ptrc> hm, with the gettext update pushed it should force builders to rebuild the older version
2025-03-30 15:04:40 <ptrc> hopefully
2025-03-30 15:04:46 <ikke> yes
2025-03-30 15:05:05 <ikke> if main is finished, the old version is purged
2025-03-30 15:05:09 <ikke> (new)
2025-03-30 15:05:21 <mio> okay (for gettext dependents?)
2025-03-30 15:05:51 <mio> algitbot: retry master
2025-03-30 15:06:01 <mio> ah nvm
2025-03-30 15:11:48 <ikke> mariadb also needs a lower version
2025-03-30 15:19:55 <mio> algitbot: retry master
2025-03-30 15:24:23 <mio> algitbot: retry master
2025-03-30 15:25:26 <mio> clang16 and uswsgi could use a ~2.13 as well
2025-03-30 15:25:28 <mio> algitbot: retry master
2025-03-30 15:25:46 <mio> algitbot: retry master
2025-03-30 15:31:15 <ptrc> algitbot: retry master
2025-03-30 15:32:57 <mio> algitbot: retry master
2025-03-30 15:33:10 <mio> algitbot: retry master
2025-03-30 15:34:39 <mio> algitbot: retry master
2025-03-30 15:35:10 <mio> algitbot: retry master
2025-03-30 15:35:16 <mio> ERROR: unable to select packages:
2025-03-30 15:35:18 <mio>   libxml2-2.14.0-r0:
2025-03-30 15:35:20 <mio>     breaks: libxml2-dev-2.13.7-r1[libxml2=2.13.7-r1]
2025-03-30 15:35:22 <mio>     satisfies: libxslt-1.1.43-r2[so:libxml2.so.16]
2025-03-30 15:35:24 <mio>                llvm18-libs-18.1.8-r4[so:libxml2.so.16]
2025-03-30 15:35:26 <mio>                libxml2-utils-2.14.0-r0[so:libxml2.so.16]
2025-03-30 15:35:48 <mio> from postgresql17 ... maybe llvm18 will need a ~2.13
2025-03-30 15:36:46 <mio> algitbot: retry master
2025-03-30 15:36:55 <mio> algitbot: retry master
2025-03-30 15:37:38 <mio> algitbot: retry master
2025-03-30 15:37:48 <mio> algitbot: retry master
2025-03-30 15:38:24 <mio> algitbot: retry master
2025-03-30 15:39:46 <mio> algitbot: retry master
2025-03-30 15:39:51 <mio> algitbot: retry master
2025-03-30 15:39:57 <mio> algitbot: retry master
2025-03-30 15:41:10 <mio> algitbot: retry master
2025-03-30 15:43:24 <ptrc> hopefully that does a thing or two
2025-03-30 15:44:19 <mio> :)
2025-03-30 15:44:21 <mio> algitbot: retry master
2025-03-30 15:45:33 <mio> libxkbcommon would need ~2.13
2025-03-30 15:45:43 <ptrc> huh, the ocaml stuff doesn't even use libxml2
2025-03-30 15:45:47 <ptrc> that's just a random failure
2025-03-30 15:46:11 <mio> yeah, that's unrelated
2025-03-30 15:47:01 <mio> maintainer notified
2025-03-30 16:00:50 <mio> algitbot: retry master
2025-03-30 16:11:29 <ikke> algitbot: retry master
2025-03-30 16:18:19 <mio> algitbot: retry master
2025-03-30 16:18:29 <mio> algitbot: retry master
2025-03-30 16:19:01 <mio> llvm16 ~2.13 (from clang16 on armv7)
2025-03-30 16:19:29 <mio> ERROR: unable to select packages:
2025-03-30 16:19:31 <mio>   so:libxml2.so.16 (no such package):
2025-03-30 16:19:33 <mio>     required by: llvm16-libs-16.0.6-r11[so:libxml2.so.16]
2025-03-30 16:20:05 <mio> algitbot: retry master
2025-03-30 16:20:17 <ikke> huh
2025-03-30 16:21:06 <mio> algitbot: retry master
2025-03-30 16:21:22 <ikke> where does libxml2.so.16 come from?
2025-03-30 16:21:38 <mio> the newer libxml2?
2025-03-30 16:21:44 <ikke> .so.16
2025-03-30 16:22:00 <mio> yeah, it went from .so.2 -> .so.16
2025-03-30 16:22:05 <mio> algitbot: retry master
2025-03-30 16:22:22 <mio> py3-lxml looking for libxml2-dev-2.14.0-r0[libxml2=2.14.0-r0]
2025-03-30 16:22:22 <ikke> oh, funny
2025-03-30 16:22:48 <mio> https://discourse.gnome.org/t/libxml2-2-14-0-released/28025
2025-03-30 16:22:58 <mio> "Binary compatibility is restricted to versions 2.14 or newer. On ELF
2025-03-30 16:23:00 <mio> systems, the soname was bumped from libxml2.so.2 to libxml2.so.16."
2025-03-30 16:24:02 <mio> for ocaml, maintainer mentioned it may need multiple retries on armv7 (unrelated to libxml2)
2025-03-30 16:25:07 <ikke> llvm16-libs-16.0.6-r11 depends on:
2025-03-30 16:25:09 <ikke> so:libxml2.so.16
2025-03-30 16:25:15 <ikke> on armv7
2025-03-30 16:26:54 <mio> clang16 then doesn't reinfoce on llvm16?
2025-03-30 16:27:12 <mio> s/reinfoce/reinforce/ the ~2.13 requirement
2025-03-30 16:27:37 <mio> algitbot: retry master
2025-03-30 16:27:43 <mio> not sure then
2025-03-30 16:28:12 <mio> algitbot: retry master
2025-03-30 16:28:59 <ptrc> llvm16 doesn't have the constraint
2025-03-30 16:29:26 <mio> yeah
2025-03-30 16:41:51 <mio> algitbot: retry master
2025-03-30 16:47:37 <ptrc> ah, that's still pulling the new version
2025-03-30 16:47:51 <ptrc> and it's gonna get purged only on successful repo build..
2025-03-30 16:49:52 <ikke> I already constrained it
2025-03-30 17:02:33 <ptrc> algitbot: retry master
2025-03-30 17:03:23 <ptrc> armv7 seems to be almost there, once it uploads i'll try to go over the apkindex and see if there's anything left to rebuild
2025-03-30 17:03:26 <ptrc> same with all the others
2025-03-30 17:03:58 <ptrc> algitbot: retry master
2025-03-30 17:04:18 <ptrc> it would also be nice to improve `ap` somehow, but i'm not sure how to even approach that
2025-03-30 17:06:34 <ikke> what you want to improve?
2025-03-30 17:09:13 <ptrc> to be fair, i'm not sure if that's something for ap or abuild, but i've been thinking if there's a way to restrict build dependencies (versions?) to only what's available in current aports
2025-03-30 17:09:52 <ikke> Would be abuild
2025-03-30 17:10:20 <ptrc> but then, abuild is already its own separate tool, so it would be hard to make changes like this
2025-03-30 17:10:48 <ikke> sorry, not following
2025-03-30 17:11:17 <ptrc> as in, people use abuild outside of aports
2025-03-30 17:11:21 <ikke> ah
2025-03-30 17:11:30 <ptrc> so we can't make changes that would hardcode some aports-related stuff
2025-03-30 17:11:34 <ptrc> at least not easily
2025-03-30 17:11:42 <ikke> It could as long as it's opt-in
2025-03-30 17:12:18 <ikke> maybe we could add cleanoldpkg as cleanup function
2025-03-30 17:12:37 <ikke> Not sure if that would cause issues
2025-03-30 17:14:18 <ikke> algitbot: retry master
2025-03-30 17:15:09 <ptrc> yeah.. i wish there was an easier way to test build infra changes like this
2025-03-30 17:15:45 <ptrc> like, a version of aports with made up problems and emulating git pushes to see how the builders react
2025-03-30 17:17:07 <ptrc> not even mentioning the "oops, actually builders work slightly differently than CI" issues
2025-03-30 17:20:39 <ptrc> algitbot: retry master
2025-03-30 17:20:40 <mio> algitbot: retry master
2025-03-30 17:20:46 <mio> oops
2025-03-30 17:28:31 <mio> algitbot: retry master
2025-03-30 17:29:13 <mio> algitbot: retry master
2025-03-30 17:30:38 <mio> postgresql16 ~2.13?
2025-03-30 17:31:08 <ptrc> might be needed
2025-03-30 17:31:30 <mio> yeah, still looking for newer version on x86_64
2025-03-30 17:32:44 <ikke> "see previous commits" 🙃
2025-03-30 17:33:08 <mio> :)
2025-03-30 17:33:25 <mio> algitbot: retry master
2025-03-30 17:41:22 <mio> algitbot: retry master
2025-03-30 17:42:22 <mio> algitbot: retry master
2025-03-30 17:45:35 <mio> algitbot: retry master
2025-03-30 17:50:47 <ptrc> i mean, the past ~20 commits to master have been about the same thing, at this point being a little vague shouldn't hurt too much.. :p
2025-03-30 17:51:23 <ptrc> though i guess if someone looks at the log/blame for a specific package, it doesn't really help, fair
2025-03-30 17:51:46 <ikke> ahuh
2025-03-30 17:52:07 <mio> s390x looks to be only arch at this point to not have the latest rebuild set
2025-03-30 17:52:40 <mio> the others should be on their way to clearing
2025-03-30 17:55:17 <ptrc> eh, most are still at least an hour from completing
2025-03-30 17:55:21 <ptrc> mostly because of the llvms
2025-03-30 17:55:41 <ptrc> why do we even keep llvm15
2025-03-30 17:56:06 <mio> ghc
2025-03-30 17:56:24 <ptrc> ah
2025-03-30 17:57:22 <ptrc> even gentoo locks it at 15, damn
2025-03-30 17:59:59 <ptrc> 16 is needed for postgres + a few random things, 17.. for some random KDE IDE, apparently, and bcachefs-tools
2025-03-30 18:00:05 <ptrc> yeah nope
2025-03-30 18:00:53 <mio> algitbot: retry master
2025-03-30 18:01:59 <ptrc> gm, why did netcf try to rebuild before augeas? that's odd
2025-03-30 18:02:01 <ptrc> s/gm/hm/
2025-03-30 18:08:52 <mio> did netcf get a ~2.13?
2025-03-30 18:09:49 <mio> just looking at -r13, it has a libxml2-dev dependency
2025-03-30 18:11:18 <mio> algitbot: retry master
2025-03-30 18:13:33 <mio> algitbot: retry master
2025-03-30 18:15:06 <mio> s390x should have the latest set this time
2025-03-30 18:35:20 <mio> algitbot: retry master
2025-03-30 18:43:44 <mio> algitbot: retry master
2025-03-30 18:48:25 <mio> algitbot: retry master
2025-03-30 18:48:55 <mio> algitbot: retry master
2025-03-30 19:01:25 <mio> algitbot: retry master
2025-03-30 19:06:16 <ptrc> algitbot: retry master
2025-03-30 19:07:42 <mio> algitbot: retry master
2025-03-30 19:08:00 <mio> algitbot: retry master
2025-03-30 19:12:21 <mio> armv7 is rebuilding the correct order
2025-03-30 19:13:09 <mio> wonder if a package is cached on other arches
2025-03-30 19:13:27 <mio> in the case of netcf/augeas
2025-03-30 19:13:41 <mio> algitbot: retry master
2025-03-30 19:31:38 <mio> algitbot: retry master
2025-03-30 19:42:32 <mio> algitbot: retry master
2025-03-30 19:43:09 <mio> algitbot: retry master
2025-03-30 19:43:15 <mio> ERROR: unable to select packages:
2025-03-30 19:43:17 <mio>   libxml2-2.14.0-r1:
2025-03-30 19:43:19 <mio>     breaks: libxml2-dev-2.13.7-r1[libxml2=2.13.7-r1]
2025-03-30 19:43:21 <mio>     satisfies: wayland-dev-1.23.1-r2[so:libxml2.so.16]
2025-03-30 19:43:23 <mio>                libxml2-utils-2.14.0-r1[so:libxml2.so.16]
2025-03-30 19:43:43 <mio> (from libxbcommon)
2025-03-30 19:43:59 <ptrc> oh, wayland-dev
2025-03-30 19:44:17 <mio> and netcf, augeas-libs-1.12.0-r9[so:libxml2.so.16]
2025-03-30 19:45:01 <ptrc> i already bumped augeas-libs and netcf
2025-03-30 19:45:03 <mio> algitbot: retry master
2025-03-30 19:45:09 <mio> okay, thanks
2025-03-30 19:45:26 <ptrc> no idea why aarch64 picks the wrong one though :/
2025-03-30 19:45:28 <mio> armv7 does build it in the correct order
2025-03-30 19:45:35 <mio> not sure
2025-03-30 19:45:47 <mio> i.e. why it doesn't on the others
2025-03-30 19:49:00 <mio> x86 looks to be okay too
2025-03-30 20:00:09 <mio> algitbot: retry master
2025-03-30 20:01:15 <ptrc> ugh, why does it keep doing this..
2025-03-30 20:01:29 <ptrc> ohhhhhh
2025-03-30 20:01:36 <ptrc> augeas got rebuilt. with the new libxml, still
2025-03-30 20:04:39 <mio> algitbot: retry master
2025-03-30 20:04:46 <mio> netcf itself may need it as well
2025-03-30 20:09:18 <mio> algitbot: retry master
2025-03-30 20:10:56 <ptrc> wait what
2025-03-30 20:11:01 <ptrc> what's the issue now
2025-03-30 20:11:08 <ptrc>     breaks: libxml2-dev-2.14.0-r1[libxml2=2.14.0-r1]
2025-03-30 20:11:08 <ptrc>                augeas-libs-1.12.0-r10[so:libxml2.so.2]
2025-03-30 20:11:08 <ptrc>     conflicts: libxml2-2.14.0-r1
2025-03-30 20:11:08 <ptrc>     satisfies: libxslt-1.1.43-r3[so:libxml2.so.2]
2025-03-30 20:11:08 <ptrc>   libxml2-2.13.7-r1:
2025-03-30 20:11:09 <ptrc>   libxml2-2.14.0-r1:
2025-03-30 20:11:09 <ptrc>     conflicts: libxml2-2.13.7-r1
2025-03-30 20:11:11 <ptrc>                libxml2-utils-2.14.0-r1[so:libxml2.so.16]
2025-03-30 20:11:11 <ptrc>     satisfies: libxml2-dev-2.14.0-r1[libxml2=2.14.0-r1]
2025-03-30 20:11:13 <ptrc> this is so stupid
2025-03-30 20:11:57 <ptrc> it literally has a version of libxml2 that works just fine
2025-03-30 20:12:00 <ptrc> why does it not pick it
2025-03-30 20:12:03 <ikke> augeas is still pulling it in
2025-03-30 20:12:09 <ikke> augeas-libs-1.12.0-r10[so:libxml2.so.2]
2025-03-30 20:13:35 <ptrc> .so.2 is the correct version
2025-03-30 20:13:37 <mio> think it's not augeas, but netcf itself selecting for the higher version
2025-03-30 20:13:47 <mio> or not augeas this time
2025-03-30 20:14:07 <ikke> right 🤐
2025-03-30 20:14:22 <mio> not sure if it's because multiple versions of the package is cached on the builder
2025-03-30 20:14:28 <ptrc> anyway, the new armv7 index looks good
2025-03-30 20:14:32 <mio> :)
2025-03-30 20:14:45 <ikke> mio: previous packages are only pruned at the end
2025-03-30 20:15:07 <ptrc> aarch64 is very broken though
2025-03-30 20:15:14 <mio> ah okay ... so as long as it hasn't uploaded, it may still select for the higher one
2025-03-30 20:15:22 <ikke> mio: correct
2025-03-30 20:15:55 <ptrc> 22 packages still using the wrong libxml version, and it's the most annoying ones ( llvm, clang, etc. )
2025-03-30 20:16:16 <ptrc> https://ptrc.gay/tHkXzSpX
2025-03-30 20:16:28 <ikke> ptrc: this now succeeds on aarch64: apk add -s -t .netcf-deps augeas-dev libgcrypt-dev libnl3-dev libxml2-dev~2.13 libxslt-dev linux-headers pkgconfig readline-dev
2025-03-30 20:17:06 <ikke> what is `np`?
2025-03-30 20:17:10 <ptrc> i mean, yeah, netcf actually built, and aarch64 uploaded
2025-03-30 20:17:20 <ptrc> np is a silly wrapper over nodejs that preloads a bunch of stuff
2025-03-30 20:17:27 <ikke> ah ok
2025-03-30 20:18:22 <ptrc> but.. yeah, it loks like aarch64 is gonna need another rebuild of them all
2025-03-30 20:18:46 <ptrc> bit annoying, i guess i should have waited with the pkgrel bump until all builders got rid of bad libxml2
2025-03-30 20:19:12 <mio> py3-lxml hasn't a ~2.13 yet 
2025-03-30 20:19:27 <mio> so rebuild may need the ~2.13 on some of those
2025-03-30 20:20:04 <mio> or has aarch64 cleared cache and it won't be needed?
2025-03-30 20:20:30 <ikke> only 2.13 is available now
2025-03-30 20:21:13 <ikke> so no long necessary to add the ~2.13 constraint
2025-03-30 20:22:14 <mio> ah okay ... one more time for llvm19 (from google-cloud-cpp) and list?
2025-03-30 20:22:38 <mio> on aarch64
2025-03-30 20:28:05 <mio> algitbot: retry master
2025-03-30 20:29:05 <mio> algitbot: retry master
2025-03-30 20:30:38 <mio> aarch64 may run into deno again soon
2025-03-30 20:31:09 <mio> algitbot: retry master
2025-03-30 20:33:02 <mio> if there's going to be a rebuild might be a good time to do it the next occasion it stops
2025-03-30 20:33:22 <mio> deno takes a little while to fail each time
2025-03-30 20:34:05 <ptrc> yeah, i'm not planning to push any rebuilds until all architectures have finished building main
2025-03-30 20:34:21 <mio> ah ... armhf is currently blocked on gettext
2025-03-30 20:34:44 <ptrc> there's two broken tests now
2025-03-30 20:34:50 <ptrc> as well
2025-03-30 20:34:50 <ptrc> test-execute.sh
2025-03-30 20:35:29 <ikke> ugh, another one
2025-03-30 20:36:29 <mio> :(
2025-03-30 20:36:58 <ptrc> hopefully that one is just flake
2025-03-30 20:36:59 <ptrc> flaky
2025-03-30 20:38:13 <mio> if the plan is to cross-ref the index of all arches and do one more rebuild across them ... before that, would need to unblock gettext first
2025-03-30 20:38:44 <mio> algitbot: retry master
2025-03-30 20:38:58 <ikke> please hold on one sec when armhf fails again
2025-03-30 20:39:40 <mio> okay
2025-03-30 20:40:49 <ikke> now it's just a single test failure
2025-03-30 20:41:08 <ikke> so flaky test..
2025-03-30 20:43:01 <mio> algitbot: retry master
2025-03-30 20:58:32 <mio> algitbot: retry master
2025-03-30 20:59:26 <mio> algitbot: retry master
2025-03-30 21:00:06 <mio> algitbot: retry master
2025-03-30 21:01:39 <mio> remaining two on x86_64, icecast and py3-lxml not yet constrained
2025-03-30 21:05:31 <mio> ah, deno fails quickly now, because of clang19/llvm19
2025-03-30 21:05:41 <mio> algitbot: retry master
2025-03-30 21:06:17 <mio> algitbot: retry master
2025-03-30 21:07:24 <mio> ptrc: icecast and py3-lxml may need a constraint, to wrap up first pass on x86_64
2025-03-30 21:08:54 <mio> algitbot: retry master
2025-03-30 21:09:42 <mio> algitbot: retry master
2025-03-30 21:11:38 <mio> algitbot: retry master
2025-03-30 21:11:59 <mio> algitbot: retry master
2025-03-30 21:12:20 <ptrc> huh, x86_64 shows no packages depending on .so.16
2025-03-30 21:12:27 <ptrc> ah, no
2025-03-30 21:12:34 <ptrc> i'm getting cached index
2025-03-30 21:13:35 <ptrc> 30 packages so far
2025-03-30 21:14:41 <mio> ouch
2025-03-30 21:15:25 <mio> around the same for x86?
2025-03-30 21:15:36 <ptrc> that's in total, it's ~20 per architecture
2025-03-30 21:15:39 <ptrc> but some don't overlap
2025-03-30 21:16:35 <ptrc> it would be nice if we could just stop ppc64le / s390x
2025-03-30 21:16:40 <ptrc> and remove the bad package
2025-03-30 21:18:12 <mio> yeah
2025-03-30 21:28:27 <mio> algitbot: retry master
2025-03-30 21:29:30 <mio> algitbot: retry master
2025-03-30 21:31:05 <mio> algitbot: retry master
2025-03-30 21:31:16 <mio> algitbot: retry master
2025-03-30 21:31:44 <mio> algitbot: retry master
2025-03-30 21:31:56 <mio> algitbot: retry master
2025-03-30 21:33:05 <mio> algitbot: retry master
2025-03-30 21:33:22 <mio> algitbot: retry master
2025-03-30 21:33:37 <mio> algitbot: retry master
2025-03-30 21:39:51 <mio> algitbot: retry master
2025-03-30 21:48:14 <mio> algitbot: retry master
2025-03-30 21:52:17 <ptrc> okay, s390x left?
2025-03-30 21:52:26 <ptrc> ah, and loongarch64
2025-03-30 21:53:32 <mio> yeah, plus armhf
2025-03-30 21:54:08 <mio> armhf is a longer drag as it wants to build gettext
2025-03-30 21:54:38 <mio> which takes a while to exit
2025-03-30 21:55:18 <mio> looking into which part of the test is causing the failure, the test changed between 0.22 -> 0.23/0.24
2025-03-30 21:55:59 <mio> algitbot: retry master
2025-03-30 21:58:33 <mio> algitbot: retry master
2025-03-30 22:07:48 <mio> algitbot: retry master
2025-03-30 22:09:57 <mio> algitbot: retry master
2025-03-30 22:13:33 <ptrc> 
ACTION pokes s390x

2025-03-30 22:13:36 <ptrc> come on, do something
2025-03-30 22:19:59 <mio> :)
2025-03-30 22:20:26 <mio> not sure whether to retry armhf, it's the ~4th time in a row it tries to rebuild gettext
2025-03-30 22:20:40 <mio> as in, if it's still useful
2025-03-30 22:21:40 <ptrc> yeah, i'd say no point really
2025-03-30 22:22:33 <mio> okay
2025-03-31 00:06:02 <mio> algitbot: retry master
2025-03-31 01:02:08 <ptrc> welp, doesn't look like s390x is gonna finish anytime soon
2025-03-31 01:02:19 <ptrc> hopefully tomorrow morning it's done
2025-03-31 01:02:29 <mio> yeah
2025-03-31 01:02:40 <mio> still have to unblock armhf
2025-03-31 01:03:32 <ptrc> eh, fair
2025-03-31 01:03:56 <ptrc> i'll try to set up aports on my arm board and bisect why it breaks
2025-03-31 01:04:47 <mio> so far it seems to have something to do with this patch https://lists.gnu.org/archive/html/bug-gnulib/2024-05/msg00112.html
2025-03-31 01:05:57 <mio> reverting the changes to memtest_explicit.c and the corresponding test, and the test passes https://gitlab.alpinelinux.org/mio/aports/-/jobs/1789881
2025-03-31 01:06:41 <mio> https://gitlab.alpinelinux.org/alpine/aports/-/blob/bb945974bbe1507fc15f8a42be192cb73c345bd4/main/gettext/revert-memset-explicit.patch
2025-03-31 01:06:52 <mio> a = 0.24, b = 0.22.5
2025-03-31 01:07:44 <mio> don't know yet which specific statement or how to fix
2025-03-31 01:09:11 <mio> the change was already in ~0.23.1
2025-03-31 01:09:29 <ptrc> oh
2025-03-31 01:10:45 <mio> in case it might help a bit
2025-03-31 01:11:22 <ptrc> your patch doesn't seem like a revert of the one from ML though
2025-03-31 01:11:27 <ptrc> unless i'm reading it wrong
2025-03-31 01:11:41 <mio> no, not a direct revert
2025-03-31 01:11:58 <ptrc> hm
2025-03-31 01:12:08 <ptrc> i'll try looking at it when i'm a bit less tired then :p
2025-03-31 01:12:15 <mio> it includes the test part of it
2025-03-31 01:12:54 <mio> okay, thanks for the progress today :)
2025-03-31 01:13:14 <mio> have a good rest
2025-03-31 01:49:34 <mio> algitbot: retry master
2025-03-31 02:00:14 <mio> algitbot: retry master
2025-03-31 02:00:34 <mio> algitbot: retry master
2025-03-31 02:33:20 <mio> algitbot: retry master
2025-03-31 02:41:52 <mio> algitbot: retry master
2025-03-31 03:53:21 <mio> algitbot: retry master
2025-03-31 03:54:22 <mio> algitbot: retry master
2025-03-31 03:54:54 <mio> algitbot: retry master
2025-03-31 05:12:14 <mio> algitbot: retry master
2025-03-31 07:29:25 <mio> ptrc: if you're bisecting the gnulib repo commits, should be around these two commits, 148939f9e27bc22f293738720508511adc6ad49a ("Avoid test failures with ASAN") and e3915945e6dc78f087d86ad7a7b26b8bfd5e98c5 ("Guarantee N3322 functionality")
2025-03-31 07:29:36 <mio> potentially the latter
2025-03-31 07:31:15 <mio> with Celeste's help, so far it looks like some combination of CFLAGS (and possibly LDFLAGS) plus the commit changes results in test failure
2025-03-31 07:31:23 <mio> s/so far/found so far/
2025-03-31 07:31:43 <mio> if the flags are unset, the test passes
2025-03-31 07:36:49 <mio> ikke: unfortunately armhf has not yet completed the first round of rebuilds, retry for me keeps returning to gettext. the others are waiting for armhf, to proceed with the last round of main/ rebuilds
2025-03-31 07:45:59 <andypost[m]> algitbot: retry master
2025-03-31 08:59:04 <ptrc> ikke: any chance we can remove 2.14 from armhf repos manually?
2025-03-31 08:59:22 <ptrc> s/repos/repodest on the builder/
2025-03-31 09:00:40 <ptrc> oh huh
2025-03-31 09:00:53 <ptrc> > FAIL: test-pthread-rwlock
2025-03-31 10:24:10 <ikke> ptrc: I can run abuild cleanoldpkg to get rid of it
2025-03-31 10:58:48 <andypost[m]> algitbot: retry master
2025-03-31 15:11:48 <andypost[m]> algitbot: retry master
2025-03-31 15:36:49 <andypost[m]> algitbot: retry master
2025-03-31 15:59:56 <mio> algitbot: retry master
2025-03-31 16:02:41 <mio> andypost[m]: shared-mime-info maybe could use a ~2.13 constraint, "shared-mime-info-2.4-r4[so:libxml2.so.16]" from qemu, icewm
2025-03-31 16:06:50 <mio> no worries though if you're busy, thanks for the llvm19/clang19 ~2.13 commits
2025-03-31 16:38:40 <mio> algitbot: retry master
2025-03-31 16:41:25 <mio> algitbot: retry master
2025-03-31 19:24:06 <andypost[m]> mio: thanks, probably deno can skip the failed test
2025-03-31 19:27:18 <mio> maybe?
2025-03-31 19:29:11 <mio> there's an open issue about it, hopefully maintainer will see and is looking into it
2025-03-31 19:37:49 <mio> (one caveat being aarch64 and x86_64 testing/ are blocked by electron at the moment if it proceeds there, but maintainer is working to incorporate a fix in security upgrade)
2025-03-31 20:14:28 <mio> great, down to gettext (armhf), deno and wpewebkit (riscv64) if there aren't any surprises in x86_64/aarch64 testing/
2025-03-31 20:22:54 <ikke> might help to report gettext upstream, seems like they are responsive to those kinds of reports
2025-03-31 20:29:36 <mio> okay ... n c o p a is on it and may have more insight on the specific trigger(s)
2025-03-31 20:35:30 <ikke> mio: referene
2025-03-31 20:35:38 <ikke> reference? Or just in chat?
2025-03-31 20:39:49 <mio> just in chat? or what do you mean by reference?
2025-03-31 20:40:02 <ikke> maybe there was an issue or MR
2025-03-31 20:43:47 <mio> ah, no issue or MR yet
2025-03-31 20:44:36 <mio> have a draft MR where was trying to isolate the CFLAGS triggering the test failure
2025-03-31 20:46:42 <mio> and mentioned my initial progress in chat, hope someone more experienced could narrow down the issue more quickly
2025-03-31 20:56:48 <andypost[m]> deno looks too tricky and outdated... 
2025-03-31 20:59:16 <mio> yeah, a few modifications no longer seem to apply, e.g. not just realigning the patches
2025-03-31 20:59:54 <mio> if the plan is to upgrade
2025-03-31 21:02:35 <mio> didn't have time to look further into it before libxml2 changes, one thing noticed was one of the patches was to unset/remove bundled mozilla tls certs and related cli options. that doesn't seem to be apply to newer version anymore, or it got moved
2025-03-31 21:06:30 <ptrc> good morning
2025-03-31 21:06:37 <ptrc> how's the libxml builder status
2025-03-31 21:06:40 <mio> gm :)
2025-03-31 21:06:46 <mio> better :)
2025-03-31 21:07:06 <ptrc> i see that rv64 is building stuff with the correct version now
2025-03-31 21:07:18 <mio> trying to unblock gettext on armhf, while waiting for riscv64 to catch up
2025-03-31 21:07:26 <ptrc> hm, is it okay for me to push some more rebuilds?
2025-03-31 21:07:33 <ptrc> or do we still have to fix armhf first
2025-03-31 21:07:48 <mio> x86 is still looking for shared-mime-info with newer libxml2, hope next round of rebuidls will fix that
2025-03-31 21:08:01 <mio> not sure, ikke?
2025-03-31 21:15:28 <mio> a bit closer on how to unblock, though not yet on the why
2025-03-31 21:24:49 <mio> looks like -Os in CFLAGS triggers the test failure
2025-03-31 21:26:18 <mio> potentially something else in LDFLAGS as well, but when CFLAGS is reset without -Os and LDFLAGS is unset, the test passes
2025-03-31 21:28:33 <mio> https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/82120/pipelines sorry it's a bit messy, those are the tests ran so far
2025-03-31 21:30:18 <mio> (with default CFLAGS and LDFLAGS unset, the test fails)
2025-03-31 21:46:21 <ptrc> okay, besides llvms and clangs there's only the voip and http servers
2025-03-31 21:46:32 <ptrc> ( kamailio, asterisk, nginx, lighttpd )
2025-03-31 22:09:01 <mio> okay