2024-10-01 02:06:50 algitbot: retry master 2024-10-01 02:16:38 algitbot: retry master 2024-10-01 03:44:56 algitbot: retry master 2024-10-01 04:04:56 algitbot: retry master 2024-10-01 04:12:00 algitbot: retry master 2024-10-01 04:13:03 algitbot: retry master 2024-10-01 04:18:07 algitbot: retry master 2024-10-01 04:28:08 algitbot: retry master 2024-10-01 04:34:04 algitbot: retry master 2024-10-01 04:44:56 algitbot: retry master 2024-10-01 04:47:58 algitbot: retry master 2024-10-01 05:02:19 algitbot: retry master 2024-10-01 09:40:28 algitbot: retry master 2024-10-01 12:43:23 wut, I removed the wip... Did I seriously merge too quickly, even though locally git said everything was pushed? wtf 2024-10-01 13:02:08 PureTryOut: GitLab has an issue where for the first 5-15 seconds it will not update the MR after pushing 2024-10-01 13:02:16 and afaict it's not only ours 2024-10-01 13:06:18 fun 2024-10-01 15:49:36 algitbot: retry master 2024-10-01 15:49:44 mm... 2024-10-01 15:50:36 lol was going to ping you if a retry failed 2024-10-01 15:57:27 meh 2024-10-01 15:57:58 algitbot: retry master 2024-10-01 16:05:58 algitbot: retry master 2024-10-01 16:12:35 algitbot: retry master 2024-10-01 16:22:59 algitbot: retry master 2024-10-01 16:39:05 algitbot: retry master 2024-10-01 17:38:22 algitbot: retry master 2024-10-01 17:38:46 algitbot: retry 3.20 2024-10-01 17:38:51 algitbot: retry v3.20 2024-10-01 17:39:32 algitbot: retry 3.20-stable 2024-10-01 17:40:23 thanks 2024-10-01 17:40:33 other error this time... 2024-10-01 17:40:34 you're welcome :) 2024-10-01 17:41:13 ah. just noticed it went through on edge after a few tries 2024-10-01 18:01:35 algitbot: retry master 2024-10-01 18:47:05 algitbot: retry master 2024-10-01 18:47:41 okay, good 2024-10-01 18:54:40 almost done with dnssec-tools, just need to adjust something embedding rpath 2024-10-01 19:21:59 algitbot: retry 3.17-stable 2024-10-01 19:45:58 algitbot: retry 3.19-stable 2024-10-01 19:46:09 algitbot: retry master 2024-10-01 19:46:53 mio: oh, thanks, was not every retrying the right branch :P 2024-10-01 19:49:04 lol np 2024-10-01 20:30:49 algitbot: retry master 2024-10-01 20:33:27 algitbot: retry master 2024-10-01 20:45:36 algitbot: retry master 2024-10-01 23:14:11 algitbot: retry master 2024-10-01 23:28:56 algitbot: retry master 2024-10-01 23:30:32 ^ needs a bump of libc crate to have a chance of building successfully on loongarch64 2024-10-01 23:30:55 guess no testing/ ci for loongarch64 to catch that 2024-10-01 23:31:12 s/ci/ci at the moment/ 2024-10-01 23:41:29 tried to notify the maintainer, hopefully it will be fixed 2024-10-01 23:50:49 s/will/could/ 2024-10-02 04:28:56 algitbot: retry master 2024-10-02 06:05:32 algitbot: retry master 2024-10-02 06:39:03 algitbot: retry master 2024-10-02 06:58:13 algitbot: retry master 2024-10-02 15:11:45 soo greeen 2024-10-02 15:12:26 love it 2024-10-02 15:31:21 algitbot: retry master 2024-10-02 18:36:29 ncopa: according to the git log you already tried to fix the fortify-headers issue that networkmanager is now failing on, did the package not build somehow? 2024-10-02 18:36:51 or do builders need to be manually updated for this? it does not seem to be installed by apk according to that build log 2024-10-02 18:37:34 dont know 2024-10-02 18:37:45 https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/main/aports-build/aports-build#L197 2024-10-02 18:38:57 Installed: Available: 2024-10-02 18:38:59 fortify-headers-2.3.1-r4 = 2.3.1-r4 2024-10-02 18:39:01 on armhf 2024-10-02 18:39:46 ok. we need help with this i think 2024-10-02 18:41:35 Huh, ok 2024-10-02 18:44:51 there is also https://build.alpinelinux.org/buildlogs/build-edge-loongarch64/community/networkmanager/networkmanager-1.48.10-r1.log 2024-10-02 18:45:12 and this https://gitlab.alpinelinux.org/Celeste/aports/-/jobs/1541735 2024-10-02 18:47:11 wrong channel 2024-10-02 18:50:40 algitbot: retry master 2024-10-02 21:21:57 algitbot: retry master 2024-10-02 21:22:31 algitbot: retry master 2024-10-02 21:39:25 algitbot: retry master 2024-10-02 21:40:01 algitbot: retry master 2024-10-02 21:40:37 algitbot: retry master 2024-10-02 21:41:38 algitbot: retry master 2024-10-02 22:05:54 I wonder if !72916 is enough 2024-10-02 22:06:51 nope, something more 2024-10-02 22:06:56 is missing 2024-10-03 00:57:12 omni: Will you be merging the fortify-headers fix? 2024-10-03 01:08:37 algitbot: retry 3.20-stable 2024-10-03 01:10:12 I would prefer if someone who knew what they were doing did 2024-10-03 01:11:08 I think it's fair game now, if it doesn't work, the whole upgrade may have to be reverted 2024-10-03 01:11:20 again 2024-10-03 01:12:28 algitbot: retry 3.20-stable 2024-10-03 01:22:18 perhaps you're right 2024-10-03 01:22:44 celie: what do you think of my backd^Wpatch then? 2024-10-03 01:26:09 I think that while it may not necessarily fix every aport, something is better than nothing 2024-10-03 01:27:35 I saw that my arti test upgade failed with the same fortify-headers issue 2024-10-03 01:28:51 It will fix quite a number of aports 2024-10-03 01:30:21 Maybe together with https://github.com/jvoisin/fortify-headers/commit/f2e7f24daa it will fix even more 2024-10-03 01:32:21 examples of things currently failing that that would fix? 2024-10-03 01:32:49 Maybe the warning in libindi, but now i see it's just a warning 2024-10-03 01:35:07 Anyway, i think in the end, the fortify-headers upgrade will have to be reverted, yet again, as the last time it was tried, we didn't have GCC 14, so we didn't have to deal with the interaction between fortify and GCC 14 2024-10-03 01:37:03 algitbot: retry master 2024-10-03 01:38:03 algitbot: retry master 2024-10-03 01:38:20 algitbot: 3.20-stable 2024-10-03 01:40:16 let's see then... 2024-10-03 01:45:43 algitbot: retry master 2024-10-03 01:46:41 algitbot: retry master 2024-10-03 01:48:31 looks like it worked? 2024-10-03 01:50:07 Probably not for libindi 2024-10-03 01:50:15 but that was expected 2024-10-03 01:50:32 At least some archs are now unblocked for community/ 2024-10-03 01:54:00 algitbot: 3.20-stable 2024-10-03 01:54:03 algitbot: rerty 3.20-stable 2024-10-03 01:54:06 algitbot: retry 3.20-stable 2024-10-03 01:54:07 lol 2024-10-03 01:56:25 Great, armhf is also done 2024-10-03 01:56:27 algitbot: retry 3.20-stable 2024-10-03 01:56:35 algitbot: retry master 2024-10-03 01:58:37 and now armv7 too 2024-10-03 01:58:41 algitbot: retry master 2024-10-03 01:59:03 algitbot: retry master 2024-10-03 02:00:18 community/R will probably have to be built -U_FORTIFY_SOURCE 2024-10-03 02:00:50 main/rust seems alright now, at least on x86_64 2024-10-03 02:00:53 algitbot: retry master 2024-10-03 02:01:08 algitbot: retry master 2024-10-03 02:01:37 algitbot: retry master 2024-10-03 02:02:49 algitbot: retry master 2024-10-03 02:04:54 algitbot: retry master 2024-10-03 02:06:06 algitbot: retry master 2024-10-03 02:06:55 algitbot: retry master 2024-10-03 02:08:46 The other aport is probably indi-3rdparty 2024-10-03 02:09:38 okay 2024-10-03 02:21:19 cely: perhaps you're right, that that other upstream fortify-headers commit would fix that 2024-10-03 02:23:18 I don't think so 2024-10-03 02:23:23 It will fix the warning 2024-10-03 02:23:28 but not the FD_ISSET error 2024-10-03 02:25:06 Though i guess it's worth a try in the upgrade MR you just opened 2024-10-03 02:27:38 yeah 2024-10-03 02:29:45 oh, no, it was already applied 2024-10-03 02:30:53 Hmm, i would've expected it to silence the warning 2024-10-03 02:34:00 So, i think the consideration now becomes, does this issue need to be fix in libindi or fortify-headers 2024-10-03 02:45:31 algitbot: retry master 2024-10-03 02:47:05 algitbot: retry master 2024-10-03 03:07:26 the only thing I found when searching for "fortify-headers" and "FD_ISSET" 2024-10-03 03:11:37 Did you paste a link? I didn't see anything 2024-10-03 03:13:34 https://www.openwall.com/lists/musl/2024/08/19/4 2024-10-03 03:13:42 it got delayed 2024-10-03 03:15:43 Ok 2024-10-03 03:16:58 https://android.googlesource.com/platform/bionic/+/ref/heads/main/libc/include/sys/select.h#77 2024-10-03 03:17:10 There's a `const` there 2024-10-03 03:18:48 Ugh, typoed the link 2024-10-03 03:18:53 https://android.googlesource.com/platform/bionic/+/refs/heads/main/libc/include/sys/select.h#77 2024-10-03 03:21:47 I'm about to check out 2024-10-03 03:22:09 chimera also package fortify-headers 2.3.1 with patches https://github.com/chimera-linux/cports/tree/master/main/fortify-headers 2024-10-03 03:23:30 but not indilib 2024-10-03 03:28:24 Chimera uses Clang 2024-10-03 03:33:02 so they're to blame? 2024-10-03 03:35:17 https://github.com/jvoisin/fortify-headers/commit/fe149628eaae9748be08815d726cc56e8e492c73 2024-10-03 03:41:11 Blame what? 2024-10-03 03:42:02 I'm just not making sense, never mind 2024-10-03 03:42:29 I don't see FD_ISSET in that commit 2024-10-03 03:42:57 I think it is a new addition in this upgrade, but it is not from that commit 2024-10-03 03:54:24 algitbot: retry master 2024-10-03 03:57:45 algitbot: retry master 2024-10-03 03:59:17 algitbot: retry master 2024-10-03 04:00:06 algitbot: retry master 2024-10-03 04:03:05 algitbot: retry master 2024-10-03 04:07:47 algitbot: retry master 2024-10-03 04:27:25 algitbot: retry master 2024-10-03 04:34:51 algitbot: retry 3.20-stable 2024-10-03 07:15:55 algitbot: retry master 2024-10-03 07:18:05 algitbot: retry master 2024-10-03 07:22:17 algitbot: retry master 2024-10-03 13:01:41 ptrc: your fwupd-efi depends on py3-pefile that just got upgraded, it's probably fine 2024-10-03 13:09:10 omni: thanks for the notice ^^ 2024-10-03 13:11:04 Uh, ok one of the deps is missing a rebuild... 2024-10-03 13:11:27 why were tests disabled for cloud-init? 2024-10-03 13:12:27 omni: oh shit I didn't mean to, that was for local testing. I'll undo it 2024-10-03 13:13:38 ok 2024-10-03 13:14:55 PureTryOut: you can use `ABUILD_BOOTSTRAP=1` env to skip tests 2024-10-03 13:15:06 oh thanks that's useful! 2024-10-03 15:24:28 Does that need a pkgrel bump? 2024-10-03 15:36:29 Should be bumped to 7 2024-10-03 15:37:18 What happened to 6? 2024-10-03 15:42:41 that's the 'faulty' one 2024-10-03 15:42:58 it got reverted from 6 to 5 2024-10-03 15:43:02 the new one should be 7 2024-10-03 15:43:46 Not really following 2024-10-03 15:43:52 2.3.1-r6 2024-10-03 15:43:56 1.1-r5 2024-10-03 15:43:57 Anyway, i've purged fortify-headers with repo-tools 2024-10-03 15:44:12 Oh, sorry, you are right 2024-10-03 15:44:17 Didn't take the version into account 2024-10-03 15:44:26 ok, fine as well 2024-10-03 15:44:37 What will happen to the people that have already got 2.3.1 installed? 2024-10-03 15:44:45 apk won't downgrade without --available, right? 2024-10-03 15:44:49 correct 2024-10-03 15:46:13 Ok 2024-10-03 19:07:35 algitbot: retry 3.20-stable 2024-10-03 21:56:54 algitbot: retry master 2024-10-04 02:13:08 dammit! 2024-10-04 02:13:18 I should have squashed that commit 2024-10-04 06:47:30 algitbot: retry 3.20-stable 2024-10-05 05:52:24 algitbot: retry master 2024-10-05 06:05:44 algitbot: retry master 2024-10-05 14:03:57 algitbot: retry master 2024-10-05 14:09:54 andypost[m]: ^ seems to be failing on the same test again 2024-10-05 14:15:19 php83-* version passed, maybe same issue as in php82-* version, don't know 2024-10-05 14:42:51 algitbot: retry master 2024-10-05 14:44:06 mio: looks it was a luck when it passed in CI 2024-10-05 14:44:23 algitbot: retry master 2024-10-05 14:49:48 mio: I will report upstream later today and it needs to disable test for it 2024-10-05 15:19:29 algitbot: retry master 2024-10-05 15:20:00 andypost[m]: okay, thanks 2024-10-05 15:20:21 algitbot: retry master 2024-10-05 15:21:06 algitbot: retry master 2024-10-05 15:21:32 algitbot: retry master 2024-10-05 16:43:47 algitbot: retry master 2024-10-05 16:54:08 algitbot: retry master 2024-10-05 17:08:04 If miller fails on riscv64, feel free to disable it, and i will look into it tomorrow 2024-10-05 17:08:56 okay 2024-10-05 17:10:16 or at least will let you know if it fails lol 2024-10-05 17:12:46 Ok, it's building on riscv64 now 2024-10-05 17:12:50 algitbot: retry master 2024-10-05 17:19:09 algitbot: retry master 2024-10-05 17:30:54 algitbot: retry master 2024-10-05 17:42:36 algitbot: retry master 2024-10-05 20:00:15 fun, openboa was retagged after I merged this 2024-10-05 20:06:55 apparently they believed we already released 3.21 2024-10-06 16:00:57 algitbot: retry master 2024-10-06 17:51:22 oof 2024-10-06 18:37:15 lesigh 2024-10-06 18:37:52 www.tychosoft.com has AAAA records, but does not accept connections on ipv6 :/ 2024-10-06 18:41:50 algitbot: retry master 2024-10-07 13:37:15 algitbot: retry master 2024-10-07 13:51:17 algitbot: retry master 2024-10-07 14:18:34 algitbot: retry master 2024-10-07 14:19:41 algitbot: retry master 2024-10-07 14:26:53 algitbot: retry master 2024-10-07 14:39:17 algitbot: retry master 2024-10-07 14:49:22 algitbot: retry master 2024-10-07 14:56:44 fcolista: not sure if you might want to look into this ^ 2024-10-07 14:57:04 seems to fail despite multiple retries 2024-10-07 14:57:17 that one did not fail in the ci/cd 2024-10-07 14:57:29 let me check 2024-10-07 14:57:50 yeah, it happens sometimes 2024-10-07 15:45:53 algitbot: retry master 2024-10-07 16:57:04 algitbot: retry master 2024-10-07 20:39:24 algitbot: retry master 2024-10-07 20:48:06 algitbot: retry aarch64 2024-10-07 20:48:14 algitbot: retry master 2024-10-07 21:18:07 algitbot: retry master 2024-10-07 21:21:21 PureTryOut: ^ "so:libjsoncpp.so.25 (no such package): required by: openxr-1.1.41-r0[so:libjsoncpp.so.25]" 2024-10-07 21:21:37 I saw. openxr just requires a rebuild 2024-10-07 21:22:03 cool, just checking you're aware 2024-10-08 00:49:29 algitbot: retry master 2024-10-08 01:19:45 some aports needs to be rebuild against new jsoncpp, I'm on it 2024-10-08 01:33:17 !73202 2024-10-08 01:47:15 uh-oh... 2024-10-08 01:53:27 What happened? 2024-10-08 01:54:42 openxr, that android-translation-layer is breaking on on aarch64, doesn't want to rebuild 2024-10-08 01:55:11 so I'm thinking of reverting the jsoncpp upgrade instead 2024-10-08 01:55:24 because I need to go 2024-10-08 01:56:32 testing/powder-toy is also failing, but since it's in testing etc it's not as important 2024-10-08 01:58:52 Is it breaking on aarch64 due to a delay, or it fails on all archs? 2024-10-08 01:59:58 oh, just found https://github.com/open-source-parsers/jsoncpp/pull/1570 2024-10-08 02:05:38 Removing the `check_required_components` line fixes things? 2024-10-08 02:08:26 we'll see 2024-10-08 02:13:09 powder-toy error should be fixable with an upgrade 2024-10-08 02:13:26 <3 2024-10-08 02:14:23 the include is already upstream, also seeing another recent commit for another header include, so hopefully it is okay 2024-10-08 02:16:43 can check powder-toy just in case 2024-10-08 02:20:09 ah, might need patching 2024-10-08 02:20:23 hmm.. another openxr build issue... 2024-10-08 02:25:24 added jsoncpp-static to makedepends 2024-10-08 02:25:55 and also an upgrade commit for powder-toy 2024-10-08 02:25:59 hope this works 2024-10-08 02:34:56 ok, I'll leave powder-toy out of this 2024-10-08 02:46:40 adding a powder-toy MR ... include fixes it for existing version, the upgrade seems to have introduced a search for header that no longer exists (from libexecinfo-dev) 2024-10-08 02:49:57 might need more time to sort an upgrade 2024-10-08 03:08:07 algitbot: retry master 2024-10-08 03:20:45 \o/ 2024-10-08 03:23:24 \o/ 2024-10-08 03:25:23 So, what's new on gitlab.a.o? 2024-10-08 03:25:42 I'm thinking about closing !52463 and !61903 2024-10-08 03:25:53 They have been open for a year and half a year respectively 2024-10-08 03:26:13 No point keeping them open for longer if they're not going to be merged 2024-10-08 03:27:02 They're for aports in testing/ anyway 2024-10-08 14:04:05 algitbot: retry master 2024-10-08 14:08:17 algitbot: retry master 2024-10-08 14:39:21 algitbot: retry master 2024-10-08 14:44:59 algitbot: retry master 2024-10-08 15:26:24 I... Do things too quickly... 2024-10-08 17:22:24 algitbot: retry master 2024-10-08 22:44:54 let's see 2024-10-08 22:49:57 suspect the same for riscv64 2024-10-08 22:50:46 yup 2024-10-09 04:46:17 algitbot: retry master 2024-10-09 04:46:34 algitbot: retry master 2024-10-09 04:49:13 algitbot: retry master 2024-10-09 08:50:23 PureTryOut: I think there should have been a lowercase "add" in the commit message and also a pkgrel bump 2024-10-09 08:54:00 oh I missed the pkgrel bump, I thought that was in there. I don't care that much about the casing though 2024-10-09 08:54:42 others do 2024-10-09 08:57:44 PureTryOut: you can not care about style in your own repo, see COMMITSTYLE.md 2024-10-09 13:15:22 algitbot: retry 3.20-stable 2024-10-09 15:27:05 algitbot: retry master 2024-10-09 15:28:00 Hmm, fetch failed 2024-10-09 15:28:00 algitbot: retry master 2024-10-09 21:46:44 terminate called after throwing an instance of 'std::bad_alloc' 2024-10-09 21:46:53 algitbot: retry master 2024-10-10 04:27:32 algitbot: retry master 2024-10-10 05:06:40 bad_alloc again.. 2024-10-10 11:06:17 algitbot: retry master 2024-10-10 11:06:39 1 test timed out: 2024-10-10 12:10:43 Ok 2024-10-10 12:10:48 abuild broke, i guess 2024-10-10 12:17:43 sounds like it 2024-10-10 12:19:23 https://gitlab.alpinelinux.org/alpine/abuild/-/commit/8b1304f3435cb6fcf3011849365be057b213aa38 last that touched that 2024-10-10 12:22:32 Yeah, i was looking at that commit too 2024-10-10 12:23:51 but not familiar enough with the intricacies of shell to see why that would introduce a bug 2024-10-10 12:31:40 algitbot: retry master 2024-10-10 12:46:04 ncopa: are you looking at abuild? 2024-10-10 12:47:56 not really 2024-10-10 12:48:52 currently fighting fortify-headers 2024-10-10 12:49:46 You are planning to upgrade fortify-headers again? 2024-10-10 12:49:50 yeah 2024-10-10 12:49:52 but meh 2024-10-10 12:50:05 ACTION must find a place to hide 2024-10-10 12:50:11 stuff segfaults with fortify-headers-2.3.2 2024-10-10 12:50:19 in unexpected ways 2024-10-10 12:50:48 sounds like antithetical for what it aims to provide 2024-10-10 12:51:01 but at least, i think i have seen an issue similar to what community/R experienced (#include_next issue), and it was fixed 2024-10-10 12:54:08 sertonix has a fix for abuild !73351 2024-10-10 16:20:55 algitbot: retry master 2024-10-10 23:34:02 algitbot: retry master 2024-10-10 23:55:19 mio: thanks ^^ 2024-10-10 23:56:19 ptrc: you're welcome 2024-10-11 00:33:19 algitbot: retry master 2024-10-11 01:25:45 algitbot: retry master 2024-10-11 02:40:10 algitbot: retry master 2024-10-11 04:13:16 algitbot: retry master 2024-10-11 05:35:13 algitbot: retry master 2024-10-11 21:57:56 algitbot: retry master 2024-10-11 22:19:46 "ERROR: Cannot find wasi libraries or problem with the wasm linker." 2024-10-11 22:34:10 ptrc: ^ not sure if it's something that needs looking into 2024-10-11 22:34:45 seems to only affect edge 2024-10-11 22:35:25 ah 2024-10-11 22:35:29 llvm 2024-10-11 22:35:32 i'll.. handle it, hopefully 2024-10-11 22:36:10 okay, cheers 2024-10-12 19:15:48 cely: thank you for fixing the thunderbird failure, and sorry for not dealing with it sooner x.x 2024-10-13 01:39:29 You 2024-10-13 01:39:44 You're welcome 2024-10-13 01:39:45 * 2024-10-13 18:53:03 huh 2024-10-13 18:54:11 it succeeded 23 minutes ago in CI :/ 2024-10-13 19:02:06 algitbot: retry master 2024-10-13 19:12:36 algitbot: retry master 2024-10-13 19:16:03 ... failed socket tests 2024-10-13 19:16:12 yup 2024-10-13 19:16:15 Cannot reproduce it 2024-10-13 19:23:23 It even works if I manually run the tests on the builder 2024-10-13 19:26:38 Ok, I can reproduce it if I use fq to run abuild in the background 2024-10-13 19:27:20 timed out? 2024-10-13 19:28:14 Sounds more like whether there is a tty available or not (or something like that) 2024-10-13 19:28:42 Same if I run it with nohup 2024-10-13 19:32:58 wonder if related to https://github.com/pyradius/pyrad/issues/165 2024-10-13 19:35:58 That PR seems to already be present 2024-10-13 19:36:04 ie, no failUnless anymore 2024-10-13 19:36:30 seems the failed tests was reported, in the PR the issue reporter said the patch doesn't appearto be related 2024-10-13 19:37:15 still looking for any follow-up to the reported issue 2024-10-13 19:38:34 In MockSocket, data is only set if data is provided to the constructor, but in the tests, I never see it ever being provided 2024-10-13 19:39:01 odd, how did the tests pass ci? 2024-10-13 19:39:53 It passes if you run the tests in the foreground 2024-10-13 19:40:13 So something must make a difference between whether a tty is present or not 2024-10-13 19:46:28 `nohup .testenv/bin/python3 -m unittest discover -k testAuthDelay` reproduces it as well 2024-10-13 19:49:58 https://github.com/pyradius/pyrad/blob/master/pyrad/client.py#L155 ready here is different 2024-10-13 19:50:14 In foreground: ready: [] 2024-10-13 19:50:30 in background: ready: [(1, 1)] 2024-10-13 20:10:50 only the tests with a timeout set fail 2024-10-13 20:12:09 nvm ... wonder why only those 3 though 2024-10-13 20:12:40 the other tests use a similar _SendPacket method 2024-10-13 20:17:31 yeah, wondering the same 2024-10-14 00:12:16 ikke: not sure how to reproduce the issue in ci, but maybe you can try this patch and see if you can still reproduce the issue anymore https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/73473 2024-10-14 00:14:38 as in, the tests should pass when run in the background 2024-10-14 00:19:01 don't know exactly why the tests failed when run in the background but not in foreground, maybe it has something to do with how it handles the output of a subprocess in stdout/something with the fdnctl call in mock.py#L48 2024-10-14 00:19:33 so self.data is defined in that case and no AttributeError occurs 2024-10-14 00:21:43 with nohup or when `abuild -r` output is piped to file locally, the self.data is undefined 2024-10-14 00:22:19 so the tests failed with that before it could run the first assert 2024-10-14 00:23:25 s/run/check/ 2024-10-14 00:24:21 initialising self.data variable seems to satisfy the tests 2024-10-14 00:28:45 s/fdnctl/fcntl/ 2024-10-14 00:40:53 (the self.data part you already noted in a comment on the other MR) 2024-10-14 06:04:21 algitbot: retry master 2024-10-14 06:05:18 missing post.install script 2024-10-14 06:05:55 s/post./*.post-/ 2024-10-14 15:25:34 algitbot: retry master 2024-10-14 16:02:02 algitbot: retry master 2024-10-14 16:04:12 algitbot: retry master 2024-10-14 16:34:30 algitbot: retry master 2024-10-14 16:44:24 algitbot: retry master 2024-10-14 16:51:51 algitbot: retry master 2024-10-14 17:03:51 algitbot: retry master 2024-10-14 17:04:18