2022-01-02 09:17:51 @`D@`I@`D` U>@`S`@>`@A . t`^@ R@` a`@ i` n & s u@` p. p@ l y i `s< @` `i` s w i t h . W e< `a a m e r v A d i n g - . i r > a q 2022-01-02 09:17:53 j u s t i f y c r e a t i n g w < a r .s 2022-01-02 09:17:55 2022-01-02 09:17:55 d i d C< @ `I@`a - d< i d . 9 < \ 11 o r i t j u s t l e t i t h a p p e n 2022-01-02 09:17:57 .i f a l< Q@ a < @ e d a d i d i t W H Y t o k -@ i - 2022-01-02 09:36:27 algitbot: retry master 2022-01-02 09:36:39 algitbot: retry master 2022-01-02 20:06:41 algitbot: retry master 2022-01-02 21:47:05 algitbot: retry master 2022-01-04 16:30:44 I suspect indstate.edu blocked the x86* builders 2022-01-04 19:50:59 amazing 2022-01-04 20:02:54 this is already happening for years 2022-01-04 20:03:04 I cannot reach them from the builders 2022-01-04 20:32:32 algitbot: retry master 2022-01-05 16:14:46 algitbot: retry master 2022-01-06 21:21:48 algitbot: retry master 2022-01-06 21:22:58 algitbot: retry master 2022-01-06 21:23:19 andypost[m]: did the checksum change upstream? 2022-01-06 21:23:34 ie, the archive 2022-01-06 21:23:38 ikke: no just checked 2022-01-06 21:24:07 Well, it gets the package from distfiles 2022-01-06 21:25:09 andypost[m]: in fact, I already checked that package before 2022-01-06 21:25:15 ikke: the same checksum in 3.15 which just builded 2022-01-06 21:27:48 andypost[m]: https://tpaste.us/n5LV 2022-01-07 10:07:11 aaaarrgghhh 2022-01-07 10:07:44 gnu autotools the gift that never keeps on giving 2022-01-07 10:15:57 looks like the fix-chmod-exit-code.patch modifies buildsystem configuration files and thus autotools wants to regenerate buildsystem files but doing so is only supported with automake 1.16.4, not with automake 1.16.5? 2022-01-07 10:17:14 and if I run ./bootstrap it tells me "bootstrapping from a non-checked-out distribution is risky" so I guess we just remove the chmod exit status patch? 2022-01-07 10:30:57 🥳 2022-01-07 12:21:19 algitbot: retry master 2022-01-07 12:45:50 algitbot: retry master 2022-01-07 16:57:53 algitbot: retry master 2022-01-07 18:40:51 hah 2022-01-07 18:42:02 huh 2022-01-07 18:42:05 algitbot: retry master 2022-01-07 21:14:16 PureTryOut: sip-build not found ^ 2022-01-07 21:14:21 I saw 2022-01-07 21:14:36 strange, as that comes from the updated py3-sip which was in the same MR... 2022-01-07 21:16:11 ikke: it seems the ppc64le ci can't validate the kde certs, curl claims they are expired, but this is only on ppc 2022-01-07 21:16:38 hmm 2022-01-07 21:17:06 psykose: do you have an url> 2022-01-07 21:17:08 ? 2022-01-07 21:17:39 https://gitlab.alpinelinux.org/psykose/aports/-/jobs/586924/raw 2022-01-07 21:17:45 grep 'fetch failed' 2022-01-07 21:18:51 wtf it's pulling in the old py3-sip version... 2022-01-07 21:18:57 Ok adding version identifiers to depends I suppose... 2022-01-07 21:19:18 Oh derp, makedepends gone wrong. How did this happen 2022-01-07 21:19:25 psykose: If I run the CI container manually on the host curl just accepts it 2022-01-07 21:19:33 that is weird 2022-01-07 21:19:56 it's the same here for instance, https://gitlab.alpinelinux.org/alpine/aports/-/jobs/586663/raw 32 times 2022-01-07 21:20:01 and all the other ci does not have the issue 2022-01-07 21:20:59 psykose: let me do a system upgrade 2022-01-07 21:21:12 nope, still the same 2022-01-08 02:04:58 algitbot: retry master 2022-01-08 04:34:55 algitbot: retry master 2022-01-08 09:50:26 algitbot: retry master 2022-01-08 10:08:23 not really a clear error 2022-01-08 10:11:14 should be fixed by this commit :) 2022-01-08 10:11:28 was very incredibly confused by that 2022-01-08 10:11:34 yet another check casualty over here 2022-01-08 10:12:00 not that it was well depend'd, my fault 2022-01-08 10:12:11 these checkdepends build issues due to options=!check are hard to catch sometimes 2022-01-08 10:12:16 for sure 2022-01-08 10:12:50 there are plenty of niche enough things that break on my regular builds because of extra deps in world (not even any -dev ones) that get fixed in rootbld 2022-01-08 10:13:02 dependencies are funny things 2022-01-08 10:13:18 circular dependencies are extra fun 2022-01-08 10:13:24 double-extra 2022-01-08 10:13:35 i remember some of those from the other month that was like a chain of 8 things 2022-01-08 17:13:09 algitbot: retry master 2022-01-08 19:02:03 algitbot: retry master 2022-01-10 17:55:48 algitbot: retry master 2022-01-12 17:11:14 algitbot: retry master 2022-01-12 17:16:57 PureTryOut: this is qtwebview 2022-01-13 04:48:18 :D :D :D :D ldc fails to build now 2022-01-13 04:48:19 what trash 2022-01-13 05:01:14 undefined reference to getcontext, classic libucontext 2022-01-13 05:02:08 i wonder why that is not in musl proper 2022-01-13 05:25:45 psykose: apparently because it's not in POSIX anymore 2022-01-13 05:25:52 ah 2022-01-13 05:25:55 that makes sense 2022-01-13 05:26:17 But why is that suddenly an issue just on a rebuild? 2022-01-13 05:27:06 what even made it rebuild? -r1 was from a month ago 2022-01-13 05:28:21 https://git.alpinelinux.org/aports/commit/?id=7cc654aa0ad3 2022-01-13 05:28:37 look at commit date, not authordate 2022-01-13 05:28:43 ah right 2022-01-13 05:30:32 it's undefined in libgphobos 2022-01-13 05:30:38 i think the actual issue is from dependencies 2022-01-13 05:30:54 yes, that's what I figured 2022-01-13 05:30:59 which is provided by gcc-gdc 2022-01-13 05:31:12 Ariadne: ^ 2022-01-13 05:31:36 mhm 2022-01-13 05:31:53 its because gcc-gdc needs to be fixed to use libucontext on x86_64 2022-01-13 05:32:00 the D people need to fix their shit 2022-01-13 05:32:20 in GCC 10, they had some custom context swapping code 2022-01-13 05:32:26 in GCC 11 they changed it 2022-01-13 05:32:36 which is the problem 2022-01-13 05:32:51 makes sense 2022-01-13 05:33:25 I guess we need to disable ldc then again? 2022-01-13 05:33:57 yes, i think so 2022-01-13 05:34:01 and open a bug 2022-01-13 05:34:07 and assign it to that Phillpe LANG 2022-01-13 05:34:10 or whatever dude 2022-01-13 05:34:12 the D dude 2022-01-13 05:34:17 nod 2022-01-13 05:34:30 in GCC 12, gdc will require gdc to build 2022-01-13 05:34:42 unlike Ada there is not any pressing reason for me to care 2022-01-13 05:34:57 ie, a bootstrap issue? 2022-01-13 05:35:00 so, this really needs to be improved on the D side of things 2022-01-13 05:35:15 yes 2022-01-13 05:35:27 i mean its not hard to deal with 2022-01-13 05:35:31 we already do for Ada 2022-01-13 05:35:40 ok 2022-01-13 05:36:28 though for Ada i would like to switch to Adacore 2022-01-13 05:36:38 and away from the GCC version 2022-01-13 05:51:09 qt6-qtwebengine: /core/libblink_core.a: error adding symbols: file format not recognized 2022-01-13 05:53:51 i've had that happen in random flakes, but not sure here 2022-01-13 09:35:20 uff.. 2022-01-13 11:10:46 algitbot: retry master 2022-01-13 11:35:14 algitbot: retry master 2022-01-13 11:36:23 we'll need to cross-compile to get qt6-qtwebengine compiling on 32-bit arches... 2022-01-13 11:36:39 ugh... 2022-01-13 11:40:29 algitbot: retry master 2022-01-13 16:53:32 algitbot: retry master 2022-01-15 06:11:17 another case of missing checkdepends 2022-01-15 07:01:58 algitbot: retry master 2022-01-15 12:06:25 algitbot: retry master 2022-01-15 15:05:10 the 3.13/3.12 builders still have jenkins fialed 2022-01-15 15:05:22 think a retry should work 2022-01-15 15:05:33 algitbot: retry 3.12-stable 2022-01-15 15:05:35 algitbot: retry 3.13-stable 2022-01-15 15:05:53 ah, that's what it's called 2022-01-15 15:06:03 you specify the branchname 2022-01-15 15:06:04 just refname 2022-01-15 15:06:06 yea 2022-01-15 15:06:10 was Unsure 2022-01-15 15:06:23 You basically do the same as what happens when you push to a branch 2022-01-15 15:42:25 algitbot: retry master 2022-01-15 15:52:10 algitbot: retry master 2022-01-15 16:28:37 algitbot: retry master 2022-01-18 20:35:55 algitbot: retry master 2022-01-19 10:44:02 algitbot: retry master 2022-01-19 11:28:32 algitbot: retry master 2022-01-19 12:02:32 ikke: please kick edge-s390x - it hangs 3days bulding testing/py3-uvloop 0.16.0-r0 2022-01-19 12:03:21 Can do later 2022-01-19 16:39:54 algitbot: retry master 2022-01-19 22:23:57 algitbot: retry master 2022-01-20 05:27:32 wowa ^ 2022-01-20 06:00:24 algitbot: retry master 2022-01-20 06:47:16 ikke: looks ipv6 test fails only on s390x builder 2022-01-20 18:15:33 algitbot: retry master 2022-01-20 21:55:03 algitbot: retry 3.13-stable 2022-01-20 22:54:53 algitbot: retry master 2022-01-20 23:00:03 algitbot: retry master 2022-01-20 23:00:29 it needs a manual clean i think 2022-01-20 23:01:13 ikke: is there a reason for build.a.o to loop build-3-13-mips64 builder 2022-01-20 23:01:36 mipsmemes 2022-01-20 23:02:18 as I see it pull/upgrade/upload each second 2022-01-20 23:02:41 yes 2022-01-20 23:04:37 andypost[m]: it does not have an ssh key 2022-01-20 23:04:41 so it cant upload 2022-01-20 23:04:46 we dontallow it anymore 2022-01-20 23:10:37 thanks 2022-01-22 15:04:41 algitbot: retry master 2022-01-22 15:38:57 algitbot: retry master 2022-01-22 15:56:03 algitbot: retry master 2022-01-22 16:37:21 hmm, I cannot reproduce the caddy test failure :( 2022-01-22 16:38:01 algitbot: retry master 2022-01-22 23:13:00 algitbot retry 3.13-stable 2022-01-22 23:13:09 algitbot: retry 3.13-stable 2022-01-22 23:14:59 algitbot: retry 3.13-stable 2022-01-22 23:15:36 algitbot: retry 3.13-stable 2022-01-22 23:15:56 algitbot: retry 3.12-stable 2022-01-23 09:23:04 algitbot: retry master 2022-01-23 10:43:54 algitbot: kick master 2022-01-23 10:44:24 algitbot: retry master 2022-01-24 20:58:54 algitbot: kick master 2022-01-24 20:59:16 algitbot: retry master 2022-01-24 21:02:24 algitbot: retry master 2022-01-24 21:18:31 algitbot: retry master 2022-01-24 21:19:27 #13470\ 2022-01-25 04:19:00 algitbot: kick master 2022-01-25 04:19:12 algitbot: retry master 2022-01-25 04:31:38 algitbot: retry master 2022-01-25 10:41:09 algitbot: kick master 2022-01-25 10:41:29 algitbot: retry master 2022-01-25 18:17:23 Ariadne: ah, interesting 2022-01-25 18:17:27 Want to look into cosign 2022-01-25 18:22:06 at the very least i want to sign our minirootfs and check it in the dockerfile, but at $dayjob we are building a tool to build container images from apk directly without dockerfile :) 2022-01-25 18:22:28 aha 2022-01-25 18:23:02 In the end it's just a nested tar with a manifest 2022-01-25 18:23:06 a "docker container" is just a tarball with a json file yes 2022-01-25 18:23:58 a docker image :P 2022-01-25 18:24:00 my dream is alpine:latest container image is just generated by apk directly as part of the release, and signed with cosign 2022-01-25 18:26:23 but that would be nice 2022-01-25 18:37:10 yes 2022-01-25 18:37:16 it is nice to have nice dreams :) 2022-01-25 18:45:46 algitbot: retry master 2022-01-25 18:46:13 no space left on device.. 2022-01-25 18:51:13 algitbot: retry masterr 2022-01-25 18:51:15 algitbot: retry master 2022-01-25 20:48:25 algitbot: kick master 2022-01-25 20:52:34 is kick separate from retry 2022-01-25 20:53:14 yes 2022-01-25 20:53:18 and only works for rv64 2022-01-25 20:53:20 (for now) 2022-01-25 20:53:36 retry does not kill hanging jobs 2022-01-25 20:53:44 good to know 2022-01-25 20:54:04 it's something clandmeter hacked on the rv64 builder in docker because it hangs quite regularly 2022-01-25 20:54:09 mhm 2022-01-25 20:54:32 It's docker using qemu-user + binfmt 2022-01-25 20:54:43 the rv64 builder 2022-01-25 21:00:54 ikke: it was me used to run rv64 via ci 2022-01-25 21:02:00 there's artifacts left n runner? 2022-01-25 21:03:01 sorry? 2022-01-25 21:03:16 you mean diskspace? 2022-01-25 21:03:57 yes, ref https://gitlab.alpinelinux.org/alpine/aports/-/jobs/604977 2022-01-25 21:04:53 No, we found the issage 2022-01-25 21:04:55 issue* 2022-01-25 21:04:58 I'm fixing it now 2022-01-25 21:09:16 andypost[m]: rv64 builder is running again 2022-01-25 21:10:01 ikke: you're fast! 2022-01-25 21:11:01 ikke: is it ok to use CI this way when I need to test something specific for RV64? 2022-01-25 21:11:09 andypost[m]: yeah, sure 2022-01-25 21:11:14 as long as you do not accidentally merge it 2022-01-25 21:11:35 sure)) 2022-01-25 21:12:05 algitbot: retry master 2022-01-25 21:16:26 algitbot: I was already fixing it before :) 2022-01-26 19:27:09 psykose: " 2022-01-26 19:27:11 data/meson.build:20:5: ERROR: Function does not take positional arguments. 2022-01-26 19:27:19 ah 2022-01-26 19:27:25 how did that pass ci the time before 2022-01-26 19:27:41 classic 2022-01-26 19:27:43 ahuh 2022-01-26 19:27:45 sure, 1 sec 2022-01-26 19:27:49 it's the new meson upgrade 2022-01-26 19:27:53 yup 2022-01-26 19:28:01 we had that before when we upgraded meson 2022-01-27 17:17:54 huh? 2022-01-27 17:17:59 why are we enabling LTO on things 2022-01-27 17:18:11 the TSC has not discussed LTO yet 2022-01-27 17:18:34 they have been enabled like this for a long time 2022-01-27 17:18:42 this is like the 30th one 2022-01-27 17:18:43 ugh 2022-01-27 17:18:50 ncopa approved it, shrug 2022-01-27 17:19:33 even jirutka did a few 2022-01-27 17:19:38 i don't think it affects the main global issue much 2022-01-27 17:19:48 i mean, i guess 2022-01-28 03:05:49 the actual archive diff is a single version tag line in one file, so fine to purge 2022-01-28 05:47:35 algitbot: retry master 2022-01-28 05:48:46 it needs a purge due to the like 5 byte change i noted above (but forgot to post the actual diff) 2022-01-28 05:48:51 alternatively there is an upgrade mr as well 2022-01-28 05:50:28 I did 2022-01-28 05:50:35 good :) 2022-01-28 05:50:36 and good morning 2022-01-28 05:50:39 morning 2022-01-28 05:50:44 or whatever time-of-day 2022-01-28 05:50:48 same tz as you 2022-01-28 05:50:51 k 2022-01-28 05:50:52 though i haven't slept 2022-01-28 05:52:11 oh, moved the wrong one 2022-01-28 05:52:47 algitbot: retry maste 2022-01-28 05:52:49 algitbot: retry master 2022-01-28 22:58:56 algitbot: kick master 2022-01-28 22:59:11 algitbot: retry master 2022-01-29 16:28:53 s390x has also been stuck the whole time on p7zip 2022-01-29 16:46:55 algitbot: retry master 2022-01-29 18:11:32 algitbot: retry master 2022-01-30 12:19:14 nmeum: https://tpaste.us/ovXg 2022-01-30 12:21:25 wow 2022-01-30 12:21:59 yet another one of those passes on ci but fails on the builder things 2022-01-30 12:23:46 can you strace this test case? 2022-01-30 12:25:51 maybe just disable the test for now? I think this will be annoying to debug without builder access 2022-01-30 12:27:47 it passed on riscv but failed on all other architectures? Oo 2022-01-30 12:32:11 running it with strace now 2022-01-30 12:32:54 I also have a patch to disable the test case for now 2022-01-30 12:33:42 https://tpaste.us/jNm1 2022-01-30 12:34:47 is that the full log? it just ends with `126771 rt_sigprocmask(S`? 2022-01-30 12:35:08 126738 exit_group(0) = ? 2022-01-30 12:35:10 126738 +++ exited with 0 +++ 2022-01-30 12:35:12 that's in the paste 2022-01-30 12:35:40 oh, somehow firefox failed to load the whole paste 2022-01-30 12:35:59 The test returns with 0 though 2022-01-30 12:36:27 oh, it expects 127? 2022-01-30 12:37:32 hmhm 2022-01-30 12:37:54 Not sure if I'm invoking it correctly 2022-01-30 12:38:35 I think test-execute-main.c supports different test cases depending on a given test number 2022-01-30 12:38:42 and depending on the test number it expects a different exit status 2022-01-30 12:38:52 yes 2022-01-30 12:38:57 and test case 3 and test case 4 seem to be the ones that are failing 2022-01-30 12:39:01 there is a shell script which runs them all 2022-01-30 12:39:06 but they all return success 2022-01-30 12:45:41 hm, this will be annoying to debug without being able to reproduce it locally ':D 2022-01-30 12:46:03 It will be anoying to debug without being able to reproduce it remotely either :P 2022-01-30 12:46:09 hehe 2022-01-30 12:46:32 so you can't reproduce it on the build atm either? 2022-01-30 12:46:45 at least not by just executing ./test-execute.sh 2022-01-30 12:46:54 let me run make check 2022-01-30 12:46:56 maybe this is some sort of parallel make issue or something? 2022-01-30 12:47:43 running `make check` now 2022-01-30 12:48:29 running it with -j $(nproc) now 2022-01-30 12:49:00 nope, pass :( 2022-01-30 12:50:20 algitbot: retry master 2022-01-30 12:50:39 maybe it's just racy 2022-01-30 12:51:11 racy on most builders at the same time? 2022-01-30 12:52:10 fyi I disabled the aarch64 runner to debug 2022-01-30 12:54:16 hm 2022-01-30 12:54:30 I am confused 2022-01-30 12:55:00 does the environment you are running `make check` in differ somehow from the environment that buildrepo uses? 2022-01-30 12:55:35 buildrepo is executed by mqtt-exec, which is a rc-service 2022-01-30 12:55:43 so yes, it most definitely differs 2022-01-30 12:56:10 `setsid nohup abuild check` still passes 2022-01-30 12:58:04 both testcase 3 and testcase 4 seem to perform tests of SIGPIPE handling 2022-01-30 12:59:32 https://tpaste.us/BgPW 2022-01-30 12:59:35 that's the env variables 2022-01-30 13:00:20 I don't think it's related to environment variables but maybe bulidrepo some infers with SIGPIPE handling or something? 2022-01-30 13:00:32 but that's also just a wild guess 2022-01-30 13:00:57 I think I will just disable the test for now 2022-01-30 15:29:53 algitbot: retry master 2022-01-30 19:00:32 algitbot: retry master