2023-06-03 10:39:13 as opposed to smart typos? :P 2023-06-03 10:39:42 hey usually they're more funny 2023-06-03 17:40:49 algitbot: retry master 2023-06-04 19:59:38 samesies 2023-06-04 19:59:54 the luck though 2023-06-04 20:00:00 i *just* fixed that in libc upstream 2023-06-04 20:00:10 and the nanosecond they release it with the fix, projects need it to work 2023-06-04 20:00:22 puh 2023-06-04 20:00:32 if i hadn't fixed it all of those would just be disables 2023-06-05 07:04:15 > add stricter checks 2023-06-05 07:04:21 > stuff crashes because checks fail 2023-06-05 07:04:24 > pikachu face 2023-06-05 10:35:19 ncopa: you forgot the -lts module rebuilds for edge 2023-06-05 10:36:47 bah. will fix 2023-06-05 10:37:10 psykose: thanks for the ping! 2023-06-05 10:37:19 np :) 2023-06-05 10:41:30 and thanks for taking care of the kernel while I was on vacation 2023-06-05 10:42:57 hopefully i didn't screw anything up 2023-06-05 10:43:56 dont think you did. i had a short look and it looks good 2023-06-05 10:44:10 thanks for checking! 2023-06-05 10:44:50 how do you normally do -rpi? the function there still output e.g. a non-suffixed name (did you manually rename it after copy?) 2023-06-05 10:45:02 for the patch diff that is 2023-06-05 10:46:42 i use the https://github.com/raspberrypi/linux repo 2023-06-05 10:46:53 rpi-6.1.y branch 2023-06-05 10:47:21 when its behind a release, I usually do something like: 2023-06-05 10:47:38 make -s kernelversion # check what version rpi is on 2023-06-05 10:48:02 git chekout -b rpi-6.1.32-alpine 2023-06-05 10:48:11 git merge v6.1.32 2023-06-05 10:48:30 aha, makes sense 2023-06-05 10:48:30 resolve conflicts if any 2023-06-05 10:48:59 i guess the genpatch() in the apkbuild doesn't get used then? 2023-06-05 10:49:04 no 2023-06-05 10:49:25 you should automate what you do and put it there ^^ 2023-06-05 10:49:40 ncopa-desktop:~/src/linux-stable (linux-6.1.y-alpine)$ tpaste < diff-and-upload.sh 2023-06-05 10:49:40 https://tpaste.us/wxvP 2023-06-05 10:49:59 large 2023-06-05 10:50:00 thanks 2023-06-05 10:51:19 i shoudl also push to https://github.com/ncopa/linux for history 2023-06-05 10:51:58 maybe we should move that to alpinulinux namespace 2023-06-05 10:52:11 github.com/alpinelinux/linux-rpi or something 2023-06-05 10:54:50 ncopa-desktop:~/src/linux-stable (linux-6.1.y-alpine)$ git remote get-url ncopa 2023-06-05 10:54:50 ncopa-desktop:~/src/linux-stable (linux-6.1.y-alpine)$ git remote get-url rpi 2023-06-05 10:54:50 git@github.com:ncopa/linux.git 2023-06-05 10:54:50 https://github.com/raspberrypi/linux.git 2023-06-05 10:54:50 ncopa-desktop:~/src/linux-stable (linux-6.1.y-alpine)$ git remote get-url origin 2023-06-05 10:54:52 git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git 2023-06-05 10:58:15 might be useful but we don't apply any patches do we 2023-06-05 10:58:26 it's basically just used to generate a diff 2023-06-05 10:58:47 yes. but sometimes there are conflicts 2023-06-05 10:59:03 and sometimes the conflicts are non-trivial to solve 2023-06-05 10:59:15 may be good to have history on what we did 2023-06-05 10:59:19 in those cases 2023-06-05 11:00:28 yeah 2023-06-05 11:02:39 im diing the rpi-6.1.32-alpine now 2023-06-05 11:03:32 tbh i think you should match it with bootloader 2023-06-05 11:03:54 if you look at main/raspberrypi-bootloader and the repo https://github.com/raspberrypi/rpi-firmware 2023-06-05 11:03:55 ok? 2023-06-05 11:03:58 you can see they update it per kernel 2023-06-05 11:04:12 so it's best to match the commit of that to the kernel version 2023-06-05 11:04:36 which involves waiting a day or two but it prevents any misaligned potential breakage that happens sometimes where the bootloader needs to support some kernel change 2023-06-05 11:04:37 i think 2023-06-05 11:05:20 normally i just bump it every time after you bump the kernel to match it, but then it's a bit forgotten in stable and i'm not sure if the systems even boot or not after a year of kernel updates but no bootloader changes 2023-06-05 11:05:24 maybe we're just lucky :) 2023-06-05 11:06:15 i run the things on my rpi4 but just edge 2023-06-05 11:07:27 hum 2023-06-05 11:08:23 i havent heard about anh problems so far, but yeah, maybe we are just lucky 2023-06-05 11:08:56 yeah i think it's not super dangerous or we would have 2023-06-05 11:10:06 i usually bump rpi kernel before stable release 2023-06-05 11:10:25 you mean between lts or just any version 2023-06-05 11:10:38 the actual versions should probably be updated like we do -lts too at some point 2023-06-05 11:11:14 there is a "verify bootloader version" on the release checklist 2023-06-05 11:11:32 aha 2023-06-05 11:11:32 so the stable branch usually gets latest bootloader 2023-06-05 18:09:58 wait, wat 2023-06-05 18:13:04 dumb thing is too popular 2023-06-05 18:13:14 even mps wants it now smh 2023-06-06 18:50:23 arrgss oppsi stable doesn't have -testing 2023-06-06 18:50:26 but dosen't hurt anyhow (: 2023-06-06 18:50:45 mb 2023-06-06 18:52:21 yeah done that before for the whole go rebuild too 2023-06-06 18:52:22 haha 2023-06-07 04:41:47 algitbot retry master 2023-06-07 04:42:07 psykose: algitbot is not responding anymore 2023-06-07 04:42:13 algitbot: retry master 2023-06-07 04:42:15 n/m 2023-06-07 04:42:32 response passed 2023-06-07 22:16:37 algitbot: retry master 2023-06-07 22:21:17 algitbot: retry master 2023-06-07 23:48:21 algitbot: retry master 2023-06-07 23:49:03 not clear why the test pass in CI but fails on the builder 2023-06-08 01:37:40 algitbot: retry master 2023-06-08 11:36:38 algitbot: retry master 2023-06-08 15:51:41 algitbot: retry master 2023-06-10 16:34:34 algitbot: retry master 2023-06-10 18:20:53 Openexr: Core Test failed: a == b 2023-06-10 18:22:33 already skipped that one 2023-06-10 18:22:46 unsurprisingly it's one of like 10 failed ones all reported already for the past year 2023-06-10 21:06:37 algitbot: retry master 2023-06-10 21:06:40 algitbot: retry 3.18-stable 2023-06-10 21:18:19 algitbot: retry 3.18-stable 2023-06-11 06:45:25 algitbot: retry master 2023-06-11 06:45:27 algitbot: retry 3.18-stable 2023-06-11 08:06:16 algitbot: retry master 2023-06-11 08:06:17 algitbot: retry 3.18-stable 2023-06-11 23:02:00 algitbot: retry 3.18-stable 2023-06-12 00:43:58 algitbot: retry 3.18-stable 2023-06-12 00:45:12 welp, the aarch64 builder seems stuck on 'failed' 2023-06-12 04:54:56 ptrc: doesn't help that the network goes down every couple of minutes 2023-06-12 09:31:00 algitbot: retry 3.18-stable 2023-06-12 20:01:18 algitbot: retry master 2023-06-12 20:03:00 set up something to automatically send retries 2023-06-12 20:03:28 psykose: well, easier to set the builder to keep building :P 2023-06-12 20:03:32 but that would also spam alot 2023-06-12 20:03:58 i prefer the retries tbh 2023-06-12 20:04:43 yes, that's why we don't enable that option except when bootstrapping 2023-06-12 21:00:29 algitbot: retry master 2023-06-12 21:02:04 algitbot: retry master 2023-06-12 21:51:44 well i guess it doesn't hang anymore for sure 2023-06-12 21:53:25 ikke: could you cycle 3.18 to put the fix in there too 2023-06-13 04:35:33 heh 2023-06-13 04:35:38 you still have merge commits enabled for that 2023-06-13 04:36:24 psykose: I prefer semi-linear history 2023-06-13 04:36:43 the only thing I wish is that there would be an option to ff for single commit mrs 2023-06-13 04:37:41 ah, yeah i see what you mean 2023-06-13 04:39:46 'units of work' rather than commit linear 2023-06-13 04:40:08 i wish it was slightly better visualised though as it ends up looking a bit like a mess 2023-06-13 04:40:14 i guess that's why they usually squash to 1 2023-06-13 04:40:20 then each unit is 1 anyway 2023-06-13 04:40:56 semi-linear forces a rebase before you merge 2023-06-13 04:40:59 so you avoid the mess 2023-06-13 04:41:21 you get stacked blocks 2023-06-13 04:43:48 what's up with this one 2023-06-13 04:43:53 how is it.. not downloading 2023-06-13 04:44:05 everything else can 2023-06-13 04:45:27 Seems to be some routing issue? 2023-06-13 04:45:56 could be 2023-06-13 04:46:03 traceroute stops after 7 hops 2023-06-13 04:46:12 that sounds like a ban 2023-06-13 04:46:19 where they just drop our traffic 2023-06-13 04:46:28 if last hop is to dns ip 2023-06-13 04:46:33 and not something in the middle 2023-06-13 04:48:29 i guess as a workaround you could just sync distfiles, though idk why that host would ban us from x86_64 2023-06-13 04:48:48 everywhere else I just get a complete different path 2023-06-13 04:49:50 well, makes sense cause the start is very different, right 2023-06-13 04:49:59 unless you get a diff path even just from same-dc-different-machine 2023-06-13 05:08:48 algitbot: retry master 2023-06-13 05:15:37 whadya change 2023-06-13 05:15:50 ah, distfiles 2023-06-13 12:14:47 algitbot: retry master 2023-06-13 12:15:05 algitbot: retry 3.18-stable 2023-06-13 16:35:03 algitbot: retry 3.18-stable 2023-06-13 17:16:28 algitbot: retry 3.18-stable 2023-06-13 19:07:42 algitbot: retry 3.18-stable 2023-06-13 19:53:09 algitbot: retry 3.18-stable 2023-06-13 20:48:21 ACTION feels another fix incoming 2023-06-13 21:06:48 classic 2023-06-14 00:45:18 algitbot: retry master 2023-06-14 01:53:02 algitbot: retry master 2023-06-14 02:27:47 algitbot: retry master 2023-06-14 02:28:04 algitbot: retry 3.18-stable 2023-06-14 04:36:19 algitbot: retry master 2023-06-14 04:36:39 seems like aarch64 does not announce here 2023-06-14 04:37:27 algitbot: retry master 2023-06-14 04:51:37 Cannot find mkstemps nor mkstemp on this platform. 2023-06-14 09:37:29 algitbot: retry master 2023-06-14 12:42:41 algitbot: retry master 2023-06-14 12:54:01 algitbot: retry master 2023-06-14 15:34:05 psykose: thank you for taking care of those ^^ 2023-06-14 15:39:41 dotnet still there but that will take a while 2023-06-14 15:39:45 thankfully just edge 2023-06-14 15:39:55 also aarch64 seems stuck and something from stderr was printed to mqtt 2023-06-14 15:39:56 weird 2023-06-14 15:40:10 I saw that earlier on armhf 2023-06-14 19:21:07 algitbot: retry master 2023-06-15 20:43:33 buildlogs for build-edge-aarch64: https://build.alpinelinux.org/buildlogs/build-edge-aarch64/community/qt5-qtwebengine/qt5-qtwebengine-5.15.14-r2.log :) 2023-06-15 21:20:03 g++: fatal error: Killed signal terminated program cc1plus 2023-06-15 21:20:05 is that oom? 2023-06-15 21:21:52 algitbot: retry master 2023-06-16 05:22:54 psykose: how can we limit the amount of jobs in qt5-qtwebengine? I've set jobs lower, but it still seems to use all cores 2023-06-16 05:23:07 (and thus memory) 2023-06-16 07:06:16 would it help if i moved the server back to che? 2023-06-16 07:06:23 its idle now, right? 2023-06-16 09:49:42 algitbot: retry master 2023-06-16 13:31:19 algitbot: retry master 2023-06-16 14:21:06 algitbot: retry 2023-06-16 14:21:47 algitbot: retry master 2023-06-16 16:22:04 algitbot: retry master 2023-06-16 17:20:27 algitbot: retry master 2023-06-16 17:23:46 https://download.eclipse.org/eclipse/updates/4.28-I-builds/I20230511-1800 -> 404 2023-06-16 17:32:38 love that 2023-06-16 17:33:31 works for me though so sounds like some ipv4 issues 2023-06-16 17:34:15 psykose: didn't 2023-06-16 17:34:17 work for me 2023-06-16 17:34:22 hm 2023-06-16 17:35:51 the aur package uses https://download.eclipse.org/jdtls/milestones/1.24.0/jdt-language-server-1.24.0-202306011728.tar.gz for source 2023-06-16 17:36:14 but non-predictable url 2023-06-16 17:36:41 i mean the failure is after the source 2023-06-16 17:36:44 it's in the mvn commands 2023-06-16 17:36:47 yes 2023-06-16 17:36:51 was aware 2023-06-16 17:39:29 hm 2023-06-16 17:39:34 not really sure what's different then 2023-06-16 17:39:38 or why it works for me 2023-06-16 17:40:24 works in dev container too 2023-06-16 17:45:25 algitbot: retry master 2023-06-16 17:47:58 algitbot: retry master 2023-06-16 17:51:40 well got past that step 2023-06-16 17:52:05 now it's just plain broken 2023-06-16 18:55:34 algitbot: retry masater 2023-06-16 18:55:36 algitbot: retry master 2023-06-17 20:51:03 FAIL test-getcwd.sh (exit status: 8) 2023-06-17 20:53:19 or might just be 0 2023-06-17 20:53:31 failing part is if (c && strlen (c) != cwd_len) 2023-06-17 20:54:13 was just stracing the test 2023-06-17 20:56:11 stat("/bin;/bin/sh", 0x7fffc9238930) = -1 ENOENT (No such file or directory) 2023-06-17 20:56:13 sus 2023-06-24 11:11:43 checksum error ^ 2023-06-24 11:12:08 sorry, patch failing to apply, not checksum 2023-06-24 11:12:36 already fixed aboev 2023-06-24 11:13:53 ah, missed it 2023-06-24 11:21:42 algitbot: retry master 2023-06-24 19:12:40 algitbot: retry 3.14-stable 2023-06-26 15:45:54 algitbot: retry master 2023-06-28 17:22:18 algitbot: retry master 2023-06-29 18:05:21 algitbot: retry 3.18-stable 2023-06-29 18:06:10 algitbot: retry 3.18-stable 2023-06-29 18:38:48 algitbot: retry 3.18-stable 2023-06-29 18:41:53 algitbot: retry 3.18-stable 2023-06-30 09:23:13 algitbot: retry 3.18-stable 2023-06-30 16:02:25 hmm, interesting, edge does report errors 2023-06-30 16:03:25 algitbot: retry master 2023-06-30 16:09:48 FileNotFoundError: [Errno 2] No such file or directory: '.dist/*.whl' 2023-06-30 16:14:23 already fixed that, just takes a while to cycle through