2023-08-01 02:13:47 <andypost[m]>   algitbot retry master
2023-08-01 02:14:11 <andypost[m]> algitbot: retry master
2023-08-01 02:18:45 <andypost[m]> algitbot: retry master
2023-08-02 06:23:04 <zcrayfish> print test
2023-08-02 06:23:15 <zcrayfish> print -buffer test
2023-08-02 16:53:49 <ikke> algitbot: retry master
2023-08-02 18:01:32 <ikke> algitbot: retry master
2023-08-02 18:39:26 <ikke> algitbot: retry master
2023-08-02 18:41:38 <ikke> go home, you're drunk
2023-08-02 18:41:40 <ikke> algitbot: retry master
2023-08-02 18:49:58 <ikke> algitbot: retry master
2023-08-02 19:27:16 <ikke> algitbot: retry master
2023-08-02 20:08:53 <ikke> algitbot: retry master
2023-08-02 20:16:51 <ikke> algitbot: retry master
2023-08-02 21:03:06 <ikke> algitbot: retry master
2023-08-03 04:57:34 <ikke> algitbot: retry master
2023-08-03 07:52:21 <ptrc> algitbot: retry master
2023-08-03 07:52:27 <ptrc> algitbot: retry 3.18-stable
2023-08-03 08:30:19 <ptrc> algitbot: retry 3.18-stable
2023-08-03 08:56:39 <ptrc> algitbot: retry 3.18-stable
2023-08-03 10:41:22 <ikke> algitbot: retry 3.18-stable
2023-08-03 16:35:48 <ikke> algitbot: retry master
2023-08-03 22:14:51 <andypost[m]> algitbot: retry 3.18-stable
2023-08-03 22:39:11 <andypost[m]> algitbot: retry 3.18-stable
2023-08-04 15:40:24 <nmeum> ikke: why is sshd installed on the armv7 and armhf builders? is that intended?
2023-08-04 15:40:47 <nmeum> ah wait they are not building in a container, right?
2023-08-04 15:41:12 <ikke> they are building in an lxc container, and all builders have sshd installed
2023-08-04 15:41:48 <nmeum> alright, in that case I better disable the ssh-based test cases
2023-08-04 15:42:05 <nmeum> thanks
2023-08-04 15:42:22 <ikke> why does it only fail on those 2 arches?
2023-08-04 15:42:41 <nmeum> I think the other arches have not build it yet
2023-08-04 15:42:45 <ikke> ok
2023-08-04 15:42:47 <nmeum> aarch64 and x86_64 are busy with ghc
2023-08-04 15:43:12 <nmeum> can also wait a bit
2023-08-04 15:55:57 <nmeum> known upstream issue actually
2023-08-04 15:56:47 <ikke> algitbot: retry 3.18-stable
2023-08-04 16:01:45 <ikke> https://gitlab.alpinelinux.org/team/alpine-desktop
2023-08-04 17:04:22 <ikke> algitbot: retry master
2023-08-04 17:41:59 <ikke> nmeum: "Error: cabal: Could not resolve dependencies:
2023-08-04 17:42:01 <ikke> "
2023-08-04 17:42:16 <ikke> algitbot: retry master
2023-08-04 17:45:25 <nmeum> on i
2023-08-04 17:45:25 <nmeum> t
2023-08-04 17:57:21 <ikke> algitbot: retry master
2023-08-04 18:06:06 <ikke> algitbot: retry master
2023-08-04 18:49:19 <PureTryOut> algitbot: retry master
2023-08-04 19:03:53 <ikke> that's a new one: "package file format error" when updating hte index
2023-08-04 19:04:36 <ikke> ERROR: kdeconnect-nftables-23.04.3-r1.apk: package file format error
2023-08-04 19:16:11 <ikke> cannot reproduce the victoria-metrics test failure :(
2023-08-04 19:59:26 <ikke> yay, more to fix
2023-08-04 20:31:10 <ikke> algitbot: retry master
2023-08-04 20:34:43 <PureTryOut> damn it
2023-08-04 20:35:10 <PureTryOut> does it need another pkgrel bump? I mean it's already -r2 but it keeps complaining about -r1
2023-08-04 20:38:18 <ikke> no, I just need to fix it for each arch
2023-08-04 20:38:42 <ikke> the package in the index is corrupt and it cannot update the index while that's the case
2023-08-04 20:39:49 <PureTryOut> oh fun
2023-08-04 20:39:53 <PureTryOut> sorry for that 🙈
2023-08-04 20:43:46 <ikke> algitbot: retry master
2023-08-04 20:44:52 <ikke> that's my fault
2023-08-04 20:44:54 <ikke> algitbot: retry master
2023-08-05 15:18:14 <ikke> FAIL: tests/premature-termination.scm
2023-08-05 15:18:16 <ikke> FAIL: tests/anonymous-auth.scm
2023-08-05 20:11:42 <nmeum> looking at guile-gnutls
2023-08-05 20:13:10 <ikke> nmeum: thanks
2023-08-05 20:23:57 <nmeum> haha the tests fail if the hostname is not valid SNI server name
2023-08-05 20:23:58 <nmeum> lovely
2023-08-05 20:24:30 <ikke> because of the _ in the builder name I suppose
2023-08-05 20:26:42 <nmeum> yep
2023-08-07 07:35:31 <ncopa> algitbot: retry master
2023-08-07 12:01:07 <celie> algitbot: retry master
2023-08-07 12:09:30 <celie> Ah, switching from pythonhosted to github changed the file
2023-08-07 12:25:05 <celie> Hm, i can't login to gitlab.a.o
2023-08-07 12:25:25 <celie> ikke: help please?
2023-08-07 12:27:52 <ikke> celie: what happened?
2023-08-07 12:30:34 <celie> Now it's working again
2023-08-07 12:31:13 <celie> Sorry, must have tried too many times...does that block you out of git pull for a while as well?
2023-08-07 12:32:50 <ikke> Not sure, never experienced it myself 
2023-08-07 12:33:42 <celie> Alright, but it's working again so all good, sorry for pinging you here
2023-08-07 12:35:50 <ikke> celie: fyi, there's also the #alpine-infra channel for these kinds of things
2023-08-07 12:37:25 <celie> Thanks
2023-08-08 17:39:05 <ikke> algitbot: retry master
2023-08-08 17:47:54 <ikke> algitbot: retry master
2023-08-12 07:12:40 <ikke> algitbot: retry master
2023-08-12 07:13:57 <ikke> algitbot: retry master
2023-08-12 20:17:07 <ikke> algitbot: retry master
2023-08-12 20:23:49 <ikke> algitbot: retry master
2023-08-12 23:19:23 <ptrc> ..why is that even getting built on rv64?
2023-08-12 23:19:35 <ptrc> it has `arch="x86_64 aarch64"`
2023-08-12 23:44:06 <ptrc> ah, it was *just* enabled
2023-08-13 02:02:47 <ptrc> algitbot: retry master
2023-08-13 02:02:48 <ptrc> >:(
2023-08-13 02:09:02 <ptrc> hmmm
2023-08-13 02:09:08 <ptrc> it might be the new binutils?
2023-08-13 02:09:27 <ptrc> because nothing changed in the dependencies beyond build-base
2023-08-13 02:11:36 <ptrc> nevermind, building with binutils-2.40-r12 still has the same issue
2023-08-13 02:15:30 <celie> Searching for "seen 0, expected -0", i get https://github.com/WebAssembly/binaryen/issues/5456
2023-08-13 02:18:30 <ptrc> ohhh, gcc13
2023-08-13 02:18:34 <ptrc> that would make sense, thanks!
2023-08-13 02:19:52 <ptrc> oh, but this is applied already?
2023-08-13 02:20:01 <celie> You're welcome. So, what happened with GCC 13?
2023-08-13 02:20:38 <ptrc> ah, nevermind, i was looking at the wrong thing
2023-08-13 02:20:41 <ptrc> i'm.. not sure really
2023-08-13 02:21:11 <ptrc> they suggest undefined behaviour, and it might be that?
2023-08-13 02:25:39 <ptrc> https://godbolt.org/z/MPeY5hE5W
2023-08-13 02:25:44 <ptrc> can't reproduce it with a minimal example
2023-08-13 02:35:57 <ptrc> and trying to build binaryen with clang results in getting random segfaults from wasm-opt
2023-08-13 02:35:58 <ptrc> :)
2023-08-13 02:35:59 <celie> It seems the tests are written in some Lisp-like S-Expression thing, and the failing test thinks `min 0 -0` is `0` instead of the expected `-0`, whereas the test immediately before does `min -0 0` and gets it right. Just guessing here, perhaps there is an optimization somewhere that just returns the 1st argument?
2023-08-13 02:37:25 <ptrc> the "lisp-like s-expression thing" is actually wat syntax for webassembly
2023-08-13 02:37:46 <ptrc> the tests execute the "min" function, which in results calls the f64.min instruction
2023-08-13 02:39:24 <ptrc> it's implemented here: https://github.com/WebAssembly/binaryen/blob/version_112/src/wasm-interpreter.h#L761 -> https://github.com/WebAssembly/binaryen/blob/version_112/src/wasm/literal.cpp#L1448
2023-08-13 02:39:38 <ptrc> that's where i got the code to try and reproduce it
2023-08-13 02:40:07 <celie> Ok
2023-08-13 02:40:20 <ptrc> the wasm spec explicitly says that f64.min should return the negative zero in case the arguments are -0 and 0
2023-08-13 02:41:06 <ptrc> ( https://webassembly.github.io/spec/core/exec/numerics.html#op-fmin )
2023-08-13 04:16:44 <ptrc> algitbot: retry master
2023-08-13 05:49:57 <ikke> ptrc: the things that still need to be rebuilt against abseil-cpp should have abseil-cpp added to makedepends
2023-08-13 19:09:06 <ikke> algitbot: retry master
2023-08-13 20:03:03 <ikke> algitbot: retry master
2023-08-13 20:05:04 <ikke> nmeum: aws package seems to fail to build on rv64 
2023-08-13 20:05:06 <ikke> endpoints.init: missing section for github.com/aws/aws-sdk-go/aws/endpoints.map.init.0
2023-08-13 20:05:15 <ikke> happens with multiple packages
2023-08-13 20:05:23 <ikke> (aws go package, used as dependency)
2023-08-13 22:44:13 <ptrc> algitbot: retry master
2023-08-13 23:23:01 <ptrc> algitbot: retry master
2023-08-13 23:23:50 <ptrc> ..oops
2023-08-14 05:16:21 <nmeum> ikke: I am currently on vacation. can you open a gitlab issue? i can look into it when i get back then
2023-08-14 05:16:41 <ikke> nmeum: enjoy your vacation
2023-08-14 05:16:55 <nmeum> i will, thanks
2023-08-14 06:38:25 <ptrc> algitbot: retry master
2023-08-14 10:21:42 <ikke> algitbot: retry master
2023-08-14 10:54:32 <andypost[m]> algitbot: retry master
2023-08-14 11:21:11 <mps> ikke: xdg-desktop-portal-gnome failed because riscv still pulls libudev-zero
2023-08-14 11:21:45 <mps> I think ncopa fixed this and wonder why it is not fixed for riscv
2023-08-14 11:22:17 <ikke> Ah, good one. Probably build order related 
2023-08-14 11:22:51 <mps> or the riscv repo is not updated with this change
2023-08-14 17:35:01 <ikke> algitbot: retry master
2023-08-14 20:23:33 <ikke> algitbot: retry master
2023-08-14 21:00:25 <ikke> algitbot: retry master
2023-08-14 21:21:59 <andypost[m]> algitbot: retry master
2023-08-14 21:33:54 <andypost[m]> ikke: the fix for rv is !49860
2023-08-14 21:34:23 <andypost[m]> it also upgrading the package 
2023-08-15 05:09:43 <ikke> algitbot: retry master
2023-08-15 12:22:33 <PureTryOut> algitbot: retry master
2023-08-15 22:50:01 <andypost[m]> algitbot: retry master
2023-08-15 22:50:36 <andypost[m]> algitbot: retry 3.18-stable
2023-08-16 19:19:16 <ptrc> someone should really fix the qt5-qtwebengine, we can't have the builders building webkit 10 times per day..
2023-08-16 19:22:20 <ikke> I agree
2023-08-16 19:22:23 <ikke> but not sure what to do about it
2023-08-16 19:22:51 <ikke> #15205
2023-08-16 19:25:43 <ikke> Found an old issue where they say you should compile it on a 64-bits host :/
2023-08-16 19:53:10 <ikke> trying to build it without dbg, see if that helps
2023-08-16 21:24:46 <ikke> no dice
2023-08-18 03:16:12 <ptrc> algitbot: retry master
2023-08-18 03:16:30 <ptrc> someday we'll make it through all packages for riscv... 🥲
2023-08-18 17:07:05 <ptrc> algitbot: retry master
2023-08-18 17:07:11 <ptrc> i don't suppose that will do much
2023-08-18 17:59:44 <ptrc> algitbot: retry master
2023-08-18 20:38:19 <ikke> was trying to debug why the test is failing
2023-08-19 06:49:10 <ikke> algitbot: retry master
2023-08-19 19:22:24 <ikke> algitbot: retry master
2023-08-20 15:36:25 <ikke> all builders are up-to-date 🎉
2023-08-22 16:35:53 <ikke> nmeum: you want to enable guix again as well
2023-08-22 16:36:08 <nmeum> yea, I am aware currently testing it locally :)
2023-08-22 16:36:24 <ikke> alright :)
2023-08-22 16:52:06 <ikke> nmeum: go tool dist list -json -> go tool dist: FAILED: not a Git repo; must put a VERSION file in $GOROOT
2023-08-22 16:52:14 <ikke> on the builders, for some reason
2023-08-22 16:53:24 <nmeum> i will look into it in a sec
2023-08-22 16:56:36 <ikke> nmeum: probably to do with the go.env file
2023-08-22 16:59:28 <ikke> In my local env I hadn't updated go, but after updating it, it broke
2023-08-22 16:59:50 <ikke> go (1.20.7-r0 -> 1.21.0-r0)
2023-08-22 17:07:45 <ikke> Manually adding the version to $(go env GOROOT)/VERSION does fix it, but not sure why it's suddenly complaining
2023-08-22 17:08:27 <nmeum> i will fix it in a sec
2023-08-22 17:08:51 <ikke> sure, thanks
2023-08-22 17:08:55 <ikke> wanted to help debug it :)
2023-08-22 17:09:01 <nmeum> all good
2023-08-22 17:09:16 <nmeum> we should just ship the VERSION file in $GOROOT
2023-08-22 17:09:20 <nmeum> the file has been around for a while
2023-08-22 17:09:30 <nmeum> it just seems that go 1.21 is more strict about it's presence
2023-08-22 17:10:03 <nmeum> it's generated by go tool dist when running ./make.bash we just never installed it
2023-08-22 17:12:26 <nmeum> ikke: ^ should be fixed with that, thanks for the heads-up  and let me know if you find anything else (:
2023-08-22 17:12:44 <ikke> no problem :)
2023-08-22 17:12:47 <ikke> thanks
2023-08-22 17:14:20 <nmeum> i want to sort out our handling of the new gotoolchain feature (see #50382) and afterwards we could also rebuild everything with Go 1.21
2023-08-22 17:28:20 <ikke> nmeum: yeah, I replied on that issue
2023-08-24 00:31:05 <celie> On x86_64, "util/glob: FAIL src/test/test_util.c:4647: assert(!results) [glob FAILED]"
2023-08-24 00:31:15 <celie> algitbot: retry master
2023-08-24 00:34:24 <celie> Same error..
2023-08-24 05:19:44 <ikke> algitbot: retry master
2023-08-25 10:29:05 <ikke> algitbot: retry mater
2023-08-25 10:29:08 <ikke> algitbot: retry master
2023-08-25 10:29:39 <ikke> algitbot: retry master
2023-08-25 10:31:33 <ikke> algitbot: retry master
2023-08-25 17:13:46 <ikke> algitbot: retry master
2023-08-26 07:27:30 <ikke> algitbot: retry master
2023-08-26 09:20:55 <ikke> algitbot: retry master
2023-08-26 09:29:38 <ikke> algitbot: retry master
2023-08-26 14:10:04 <ikke> algitbot: retry master
2023-08-27 12:42:41 <ikke> algitbot: retry master
2023-08-29 10:23:12 <ptrc> algitbot: retry master
2023-08-29 10:23:50 <ptrc> ( also, `mosquitto_pub -L mqtt://msg.alpinelinux.org/git/aports/master -m ''` still triggers the builders :p )
2023-08-29 10:25:12 <clandmeter> triggers as in what?
2023-08-29 10:56:07 <ptrc> as in, same as "retry master"
2023-08-29 10:56:10 <ptrc> makes them wake up
2023-08-29 13:31:16 <rnalrd> algitbot: retry master
2023-08-29 20:50:08 <andypost[m]> algitbot: retry master
2023-08-29 20:51:57 <ikke> Package 'nss' has version '3.92', required version is '>= 3.93'
2023-08-29 20:52:24 <ikke> ptrc: seems like we need a newer nss
2023-08-29 21:00:59 <andypost[m]> ikke: the question is why only aarch64 complains about it
2023-08-29 21:01:09 <ikke> yes, good question
2023-08-29 21:01:29 <andypost[m]> and there's no 3.93 tarball yet(
2023-08-29 21:01:40 <ikke> maybe because x86_64 didnt get to it yet
2023-08-29 21:02:04 <ikke> seems to be stuck
2023-08-29 21:02:29 <ikke> algitbot: retry master
2023-08-29 21:02:32 <andypost[m]> oh, very probably
2023-08-30 01:56:32 <andypost[m]> algitbot: retry master
2023-08-30 04:51:58 <ikke> cherry-tree is deadlocked again
2023-08-30 10:55:25 <ikke> algitbot: retry 3.13-stable
2023-08-30 12:27:53 <PureTryOut> algitbot: retry master
2023-08-30 14:07:25 <PureTryOut> algitbot: retry master
2023-08-30 14:28:27 <PureTryOut> algitbot: retry master
2023-08-30 14:34:59 <PureTryOut> algitbot: retry master
2023-08-30 14:45:35 <PureTryOut> algitbot: retry master
2023-08-30 15:17:09 <PureTryOut> algitbot: retry master
2023-08-30 15:25:47 <PureTryOut> algitbot: retry master
2023-08-30 15:33:11 <PureTryOut> algitbot: retry master
2023-08-30 22:33:36 <andypost[m]> algitbot: retry master
2023-08-30 22:56:14 <andypost[m]> algitbot: retry master
2023-08-31 09:42:20 <PureTryOut> algitbot: retry master
2023-08-31 12:43:56 <PureTryOut> I'm... unsure what to do about that Neochat build failure, besides just disabling it again. Why does the compiler just segfault...?
2023-08-31 12:47:45 <ikke> I can see if I can get some more details
2023-08-31 12:57:57 <ikke> PureTryOut: it using qemu-user does not make that easy
2023-08-31 12:58:06 <ikke> I have a core file, cannot get any information out of it
2023-08-31 12:58:29 <PureTryOut> Fun 😅
2023-08-31 12:58:49 <PureTryOut> I guess I'll disable it again with an updated comment and wait for proper riscv64 hardware at least?
2023-08-31 12:59:07 <ikke> yeah, sounds like a plan
2023-08-31 13:33:04 <ikke> algitbot: retry master
2023-08-31 15:28:44 <ikke> algitbot: retry master
2023-08-31 21:22:21 <andypost[m]> algitbot: retry 3.18-stable