2023-11-01 00:33:17 <andypost[m]> algitbot: retry master
2023-11-01 00:48:55 <celie> algitbot: retry master
2023-11-01 01:58:48 <celie> Fixes for the 3.19 builders: !54511 !54512
2023-11-01 02:01:22 <celie> I am still working on !54386, managed to get it to build but now 1 test is failing due to "Subprocess aborted", will probably have to add some ctest options to get more details
2023-11-01 02:04:50 <celie> Anyway, i saw that andypost also has an MR for vtk, so if you (or anyone else) can get pass that failing test, please feel free to get that MR merged
2023-11-01 02:05:56 <andypost[m]> celie: my MR is not finished
2023-11-01 02:07:03 <celie> I know, and i think i managed to get further, but what i'm saying is i don't mind anyone taking over and building on what i've done
2023-11-01 02:08:29 <andypost[m]> I mean if it's only one test then probably better to disable it and report upstream 
2023-11-01 02:09:38 <andypost[m]> celie: is there a way to mark TestFeatureEdges as skipped?
2023-11-01 02:11:35 <celie> I think ctest has -E
2023-11-01 02:14:14 <celie> but i will wait for this run of the CI to finish, then add --rerun-failed --output-on-failure as adviced by ctest and see if that gives better information on what's causing it to fail before thinking about -E
2023-11-01 02:18:01 <andypost[m]> nice idea!
2023-11-01 03:06:22 <celie> Found a patch upstream for vtk's TestFeatureEdges, but not much information in the commit message about the error it fixes, so hopefully it is the same error
2023-11-01 03:09:12 <celie> For py3-wordcloud failing tests, i found a similar issue (but different project) at https://github.com/WhyNotHugo/python-barcode/issues/217 that mostly confirms the problem is with Pillow 10
2023-11-01 04:06:26 <celie> Nope, the patch did not work for vtk, so i've updated !54386 to exclude that failing test
2023-11-01 04:09:49 <celie> For grpc-java, i actually have a fix for it as part of !54120 (it mentions 51119 because that was the MR that first made me aware of this issue)
2023-11-01 04:11:31 <celie> In short, grpc-java hasn't been rebuilt since 3.18-stable, and the protobuf package has had a big change since then, removing the static libraries that grpc-java wants to link against
2023-11-01 04:13:17 <celie> So, in that MR, i add a protobuf-static subpackage, and build grpc-java with that instead (i also had to revert protobuf's exclude.patch for the -static subpackage to allow grpc-java to build successfully)
2023-11-01 04:14:40 <celie> chereskata added my changes to !51119 so it could pass, but i think now it's held up by some other thing failing
2023-11-01 04:19:20 <celie> I tried patching grpc-java to use the dynamic libprotoc/protobuf again today, but i still can't make it work; and half a year ago (a few days before 3.18-stable was released), grpc-java's maintainer tried updating it in !46676 but couldn't get the new version to work
2023-11-01 05:59:45 <celie> Alright, so just in case there's been too much other things since i've mentioned it, fixes for the 3.19 builders: !54511 !54512 !54513 !54516 (and probably !54120 which has a fix for grpc-java included, but that's a rather non-trivial change that affects main/protobuf, and probably someone should look it over first before i create a new MR for it, if necessary)
2023-11-01 06:41:50 <celie> I wonder if an upgrade to helix-23.10 will fix the test errors
2023-11-01 07:04:07 <celie> Nope, same error in helix-23.10
2023-11-01 07:04:51 <celie> Anyway, 1 more fix for the 3.19 builders: !54520
2023-11-01 08:37:39 <mps> fabled: sorry for annoying you, could we merge !53964
2023-11-01 12:14:23 <celie> I think there was a previous instance where fabled's aport (perl-lingua-en-inflect) was taken over when it was moved into community (!54300), but not sure if we should make an example of that (i have something that depends on one of fabled's aports that i'm thinking of moving to community as well)
2023-11-01 12:14:49 <celie> Oops, sorry, should've been !53400
2023-11-01 12:22:22 <celie> GitHub Action? :D
2023-11-01 12:30:20 <celie> ^ i have an MR for that !54520
2023-11-01 12:37:26 <celie> ^ wow, am i seeing this right? the build log for opencv almost 200MB..
2023-11-02 06:38:00 <ikke> algitbot: retry master
2023-11-02 16:22:27 <andypost[m]> algitbot: retry master
2023-11-02 17:02:35 <andypost[m]> algitbot: retry master
2023-11-02 18:36:11 <andypost[m]> algitbot: retry master
2023-11-02 18:37:36 <andypost[m]> algitbot: retry master
2023-11-02 18:47:45 <andypost[m]> algitbot: retry master
2023-11-02 18:50:38 <andypost[m]> algitbot: retry master
2023-11-02 18:55:23 <andypost[m]> algitbot: retry master
2023-11-02 18:56:01 <andypost[m]> algitbot: retry master
2023-11-02 19:03:27 <andypost[m]> algitbot: retry master
2023-11-02 19:19:48 <andypost[m]> algitbot: retry master
2023-11-02 19:24:21 <andypost[m]> algitbot: kick build-edge-riscv64
2023-11-02 19:25:24 <andypost[m]> ikke: is there a wait to restart build-edge-riscv64 it hangs since morning
2023-11-02 19:25:25 <andypost[m]> s/wait/way
2023-11-02 19:27:44 <ikke> done
2023-11-02 19:28:17 <andypost[m]> thank you
2023-11-02 19:49:21 <mps> too early for Christmas tree :)
2023-11-02 19:49:39 <mps> i.e. how looks this channel
2023-11-02 21:02:05 <andypost[m]> algitbot: retry master
2023-11-03 06:16:55 <andypost[m]> algitbot: retry master
2023-11-03 06:18:28 <andypost[m]> algitbot: retry master
2023-11-03 07:16:52 <andypost[m]> algitbot: retry master
2023-11-03 07:23:49 <andypost[m]> algitbot: retry master
2023-11-03 10:22:20 <mps> no one know fix for qt6-qtwebengine on aarch64?
2023-11-03 12:57:10 <mps> could the qt6-qtwebengine on aarch64 be disabled? it blocks builder for few days now
2023-11-03 17:28:15 <mps> algitbot: retry master
2023-11-03 17:38:42 <andypost[m]> algitbot: retry master
2023-11-03 18:37:57 <mps> could it be that builder doesn't have enough RAM qt6-qtwebengine because error is 'terminate called after throwing an instance of 'std::bad_alloc''
2023-11-03 18:38:48 <ikke> mps: the builder is a bit tight on RAM, it only has 256G
2023-11-03 18:39:16 <mps> meh :)
2023-11-04 02:31:41 <andypost[m]> algitbot:retry master
2023-11-04 02:31:52 <andypost[m]> algitbot: retry master
2023-11-04 06:08:01 <mps> algitbot: retry master
2023-11-04 07:04:53 <ikke> I don't understasnd why it would be running out of memory on a 256G box
2023-11-04 07:06:01 <ikke> It's not, at the time it failed the box still had 190G ram available
2023-11-04 07:11:05 <mps> who knows, maybe some bug somewhere which eat all memory
2023-11-04 07:13:10 <ikke> https://imgur.com/a/yVwA1kv
2023-11-04 07:33:19 <ikke> yeah, definitely not a lack of memory
2023-11-04 07:34:51 <ikke> mps: https://www.mail-archive.com/llvm-bugs@lists.llvm.org/msg69642.html
2023-11-04 07:36:43 <mps> ikke: I saw this bug report last night somewhere on github
2023-11-04 07:36:54 <ikke> yeah, it linked to https://github.com/llvm/llvm-project/issues/69245
2023-11-04 17:19:05 <andypost[m]> algitbot: retry master
2023-11-04 19:06:45 <andypost[m]> algitbot: retry master
2023-11-04 19:07:19 <andypost[m]> algitbot: retry master
2023-11-04 19:26:11 <andypost[m]> algitbot: retry master
2023-11-04 19:44:57 <andypost[m]> algitbot: retry master
2023-11-04 20:00:12 <andypost[m]> algitbot: retry master
2023-11-04 20:09:57 <andypost[m]> algitbot: retry master
2023-11-04 20:19:12 <andypost[m]> algitbot: retry master
2023-11-04 20:21:02 <andypost[m]> algitbot: retry master
2023-11-04 21:18:41 <andypost[m]> algitbot: retry master
2023-11-04 21:29:07 <andypost[m]> algitbot: retry master
2023-11-04 21:35:46 <andypost[m]> algitbot: retry master
2023-11-04 21:49:33 <andypost[m]> algitbot: retry master
2023-11-04 21:51:39 <andypost[m]> algitbot: retry master
2023-11-04 22:13:49 <andypost[m]> algitbot: retry master
2023-11-04 22:14:27 <andypost[m]> algitbot: retry master
2023-11-04 22:45:20 <andypost[m]> algitbot: retry master
2023-11-04 23:07:00 <andypost[m]> algitbot: retry master
2023-11-04 23:40:06 <andypost[m]> algitbot: retry master
2023-11-05 00:12:47 <andypost[m]> algitbot: retry master
2023-11-05 00:29:21 <andypost[m]> algitbot: retry master
2023-11-05 00:41:59 <andypost[m]> algitbot: retry master
2023-11-05 01:27:19 <andypost[m]> algitbot: retry master
2023-11-05 01:34:06 <andypost[m]> algitbot: retry master
2023-11-05 01:59:16 <andypost[m]> algitbot: retry master
2023-11-05 02:36:34 <andypost[m]> algitbot: retry master
2023-11-05 02:47:27 <andypost[m]> algitbot: retry master
2023-11-05 02:59:05 <andypost[m]> algitbot: retry master
2023-11-05 03:22:57 <andypost[m]> algitbot: retry master
2023-11-05 03:23:23 <andypost[m]> algitbot: retry master
2023-11-05 03:32:15 <andypost[m]> algitbot: retry master
2023-11-05 03:33:01 <andypost[m]> algitbot: retry master
2023-11-05 03:45:47 <andypost[m]> algitbot: retry master
2023-11-05 08:31:53 <mps> algitbot: retry master
2023-11-05 11:38:42 <andypost[m]> algitbot: retry master
2023-11-05 12:11:22 <andypost[m]> algitbot: retry master
2023-11-05 12:14:17 <andypost[m]> algitbot: retry master
2023-11-05 14:40:38 <andypost[m]> algitbot: retry master
2023-11-05 17:14:01 <andypost[m]> algitbot: retry master
2023-11-05 17:16:02 <andypost[m]> algitbot: retry master
2023-11-05 18:07:52 <andypost[m]> algitbot: retry master
2023-11-05 18:28:15 <andypost[m]> algitbot: retry master
2023-11-05 18:49:49 <andypost[m]> algitbot: retry master
2023-11-05 20:04:51 <andypost[m]> algitbot: retry master
2023-11-05 23:01:33 <andypost[m]> algitbot: retry master
2023-11-06 06:21:47 <ikke> algitbot: retry master
2023-11-06 15:50:07 <andypost[m]> algitbot: retry master
2023-11-06 16:24:19 <andypost[m]> algitbot: retry master
2023-11-06 16:41:53 <mps> algitbot: retry master
2023-11-06 20:52:03 <andypost> algitbot: retry master
2023-11-06 21:00:05 <andypost> algitbot: retry master
2023-11-07 00:53:59 <andypost> algitbot: retry master
2023-11-07 00:56:32 <andypost> algitbot: retry master
2023-11-07 01:05:11 <andypost> algitbot: retry master
2023-11-07 01:23:03 <andypost> algitbot: retry master
2023-11-07 01:29:21 <andypost> algitbot: retry master
2023-11-07 01:41:59 <andypost> algitbot: retry master
2023-11-07 02:03:26 <andypost> algitbot: retry master
2023-11-07 02:09:07 <andypost[m]> algitbot: retry master
2023-11-07 15:56:12 <andypost[m]> algitbot: retry master
2023-11-07 16:53:46 <ikke> algitbot: retry master
2023-11-07 17:37:39 <andypost[m]> algitbot: retry master
2023-11-07 17:39:58 <andypost[m]> algitbot: retry master
2023-11-08 00:56:43 <andypost[m]> algitbot: retry master
2023-11-08 01:13:49 <andypost[m]> algitbot: retry master
2023-11-08 20:55:30 <ikke> algitbot: retry master
2023-11-08 22:36:31 <andypost> algitbot: retry master
2023-11-09 00:19:57 <ptrc> also i misunderstood some things and apparently upstream didn't remove PWL but *PWL suggestions*; don't really want to push another commit just to update the comment though
2023-11-09 00:27:29 <andypost> algitbot: retry master
2023-11-09 02:00:16 <andypost> algitbot: retry master
2023-11-09 02:18:04 <andypost> algitbot: retry master
2023-11-09 02:23:52 <andypost> algitbot: retry master
2023-11-09 02:35:01 <andypost> algitbot: retry master
2023-11-09 03:34:52 <andypost> algitbot: retry master
2023-11-09 04:15:03 <andypost> algitbot: retry master
2023-11-09 04:40:35 <andypost> algitbot: retry master
2023-11-09 05:23:11 <andypost> algitbot: retry master
2023-11-09 05:26:24 <andypost> algitbot: retry master
2023-11-09 05:27:11 <andypost> algitbot: retry master
2023-11-09 05:32:28 <andypost> algitbot: retry master
2023-11-09 05:34:34 <andypost> algitbot: retry master
2023-11-09 05:47:08 <andypost> algitbot: retry master
2023-11-09 06:24:14 <andypost> algitbot: retry master
2023-11-09 07:21:57 <andypost[m]> algitbot: retry master
2023-11-09 10:11:02 <PureTryOut> algitbot: retry master
2023-11-09 14:24:08 <ikke> algitbot: retry master
2023-11-09 18:51:36 <PureTryOut> algitbot: retry master
2023-11-09 21:45:16 <PureTryOut> Fun, chromium on aarch64 fails on linking at the very end...
2023-11-09 21:45:18 <PureTryOut> algitbot: retry master
2023-11-10 03:17:53 <andypost[m]> algitbot: retry master
2023-11-10 03:22:31 <andypost[m]> algitbot: retry master
2023-11-10 03:37:21 <andypost[m]> algitbot: retry master
2023-11-10 03:53:42 <andypost[m]> algitbot: retry master
2023-11-10 04:19:08 <andypost[m]> algitbot: retry master
2023-11-10 04:37:30 <andypost[m]> algitbot: retry master
2023-11-10 04:46:37 <andypost[m]> algitbot: retry master
2023-11-10 04:53:42 <andypost[m]> algitbot: retry master
2023-11-10 04:56:08 <andypost[m]> algitbot: retry master
2023-11-10 05:04:25 <andypost[m]> algitbot: retry master
2023-11-10 09:48:20 <PureTryOut> algitbot: retry master
2023-11-10 16:07:49 <andypost[m]> algitbot: retry master 
2023-11-10 21:14:59 <ikke> algitbot: retry master
2023-11-11 00:09:25 <andypost[m]> algitbot: retry master
2023-11-11 00:20:11 <andypost[m]> s390x finished!
2023-11-11 03:09:29 <andypost[m]> algitbot: retry master
2023-11-11 08:45:43 <PureTryOut> algitbot: retry master
2023-11-11 11:27:04 <andypost[m]> algitbot: retry master
2023-11-11 14:33:52 <ikke> algitbot: retry master
2023-11-11 15:50:30 <andypost[m]> algitbot: retry master
2023-11-11 21:31:46 <ptrc> ...any clue why the download gets a different checksum? i just tried to curl the file again, and it's the same as in the APKBUILD
2023-11-11 21:32:21 <ikke> ptrc: which package?
2023-11-11 21:32:30 <ptrc> the ARM webkits
2023-11-11 21:32:41 <ptrc> both webkit2gtk and the -6.0 one
2023-11-11 21:32:53 <ikke> Fetching https://distfiles.alpinelinux.org/distfiles/edge/webkitgtk-2.42.1.tar.xz
2023-11-11 21:33:06 <ikke> I'll rename it
2023-11-11 21:33:19 <ptrc> that gives a 404 for me
2023-11-11 21:33:46 <ikke> hmm, yes, I see in the logs
2023-11-11 21:34:08 <ikke> It's confusing because at the end it still repeats the distfiiles url while it's actually downloading from upstream
2023-11-11 21:34:29 <ikke> "Partial download found. Trying to resume.
2023-11-11 21:34:30 <ikke> "
2023-11-11 21:36:57 <ikke> algitbot: retry master
2023-11-12 05:47:43 <andypost[m]> algitbot: retry master
2023-11-12 07:20:23 <ikke> algitbot: retry master
2023-11-12 07:28:47 <ikke> algitbot: retry master
2023-11-12 07:52:12 <ikke> algitbot: retry master
2023-11-12 08:07:52 <ikke> algitbot: retry master
2023-11-13 19:44:59 <andypost[m]> algitbot: retry master 
2023-11-13 19:49:54 <andypost[m]> algitbot: retry master 
2023-11-13 20:08:23 <andypost[m]> algitbot: retry master 
2023-11-14 15:42:18 <andypost[m]> algitbot: retry master
2023-11-14 16:37:29 <andypost[m]> algitbot: retry master
2023-11-14 17:04:48 <andypost[m]> algitbot: retry master
2023-11-14 17:27:23 <andypost[m]> algitbot: retry master
2023-11-14 17:46:21 <andypost[m]> algitbot: retry master
2023-11-14 17:49:47 <andypost[m]> algitbot: retry master
2023-11-14 17:54:27 <andypost[m]> algitbot: retry master
2023-11-14 17:56:33 <andypost[m]> algitbot: retry master
2023-11-14 21:16:36 <ikke> algitbot: retry master
2023-11-15 21:42:43 <andypost[m]> algitbot: retry master
2023-11-15 21:46:18 <andypost[m]> algitbot: retry master
2023-11-15 21:54:35 <andypost[m]> algitbot: retry master
2023-11-15 22:10:18 <andypost[m]> algitbot: retry master
2023-11-15 22:13:54 <andypost[m]> algitbot: retry master
2023-11-15 23:42:30 <andypost[m]> algitbot: retry master
2023-11-15 23:44:11 <andypost[m]> algitbot: retry master
2023-11-16 00:06:14 <andypost[m]> algitbot: retry master
2023-11-16 00:11:31 <andypost[m]> algitbot: retry master
2023-11-16 00:13:35 <andypost[m]> algitbot: retry master
2023-11-16 00:23:42 <andypost[m]> algitbot: retry master
2023-11-16 10:50:56 <ptrc> ..oops
2023-11-16 14:41:57 <ikke> algitbot: retry master
2023-11-17 18:05:21 <andypost[m]> algitbot: retry master
2023-11-17 21:04:50 <ikke> algitbot: retry 3.18-stable
2023-11-17 22:41:15 <ikke> algitbot: retry 3.18-stable
2023-11-18 09:03:44 <ikke> algitbot: retry master
2023-11-18 09:03:57 <ikke> algitbot: retry 3.18-stable
2023-11-18 09:23:40 <ikke> algitbot: retry 3.18-stable
2023-11-18 09:52:21 <ikke> algitbot: retry 3.18-stable
2023-11-18 17:34:15 <ikke> algitbot: retry 3.18-stable
2023-11-18 19:58:51 <ikke> algitbot: retry 3.18-stable
2023-11-18 20:30:22 <ikke> algitbot: retry 3.18-stable
2023-11-18 21:43:38 <ikke> algitbot: retry master
2023-11-19 00:10:38 <andypost[m]> algitbot: retry master 
2023-11-19 03:03:35 <celie> ^ x86 is done too
2023-11-19 03:05:36 <celie> algitbot: retry master
2023-11-19 03:13:59 <celie> ^ so it seems --dw from 2ce5b44b does not fix the build
2023-11-19 03:39:39 <celie> !55665 seems like it should be -dw instead of --dw
2023-11-19 04:38:15 <celie> ptrc: Sorry, i will look deeper into the dub thing to hopefully solve it for good
2023-11-19 04:38:33 <ptrc> oh, that didn't solve it?
2023-11-19 04:38:40 <ptrc> weh
2023-11-19 04:38:44 <ptrc> i love when upstreams do -Werror
2023-11-19 04:38:57 <ptrc> speaking of which, hm
2023-11-19 04:39:09 <ptrc> > d21: warning: unrecognized gcc debugging option: w
2023-11-19 04:39:21 <ptrc> i'll try setting up a sysroot for 3.19
2023-11-19 04:39:32 <ptrc> because it definitely behaves differently than edge in this case
2023-11-19 04:46:03 <celie> I think it's more like, `bin/dub test` chooses ldc2 as compiler on the CI, while the builders choose gdc
2023-11-19 04:46:59 <celie> which is why the build doesn't fail for aarch64, as tests are disabled htere
2023-11-19 04:48:11 <celie> https://build.alpinelinux.org/buildlogs/build-edge-x86_64/community/dub/dub-1.34.0-r0.log
2023-11-19 04:48:41 <ptrc> ohhhh
2023-11-19 04:48:41 <celie> "Starting Performing "$DFLAGS" build using ldc2 for x86_64"
2023-11-19 04:48:47 <celie> So, it chose ldc2 on edge as well
2023-11-19 04:48:56 <ptrc> that makes sense
2023-11-19 04:49:16 <ptrc> how the heck is one supposed to check which one gets chosen
2023-11-19 04:49:35 <ptrc> have you seen a way to put an explicit compiler name there?
2023-11-19 04:50:35 <celie> I'm trying it in !55668: bin/dub test --compiler=gdc
2023-11-19 04:50:41 <celie> and as expected, it fails
2023-11-19 04:50:59 <ptrc> ah wait
2023-11-19 04:51:07 <ptrc> it already has '--compiler=ldc2' tho
2023-11-19 04:51:11 <celie> So, it seems DFLAGS is actually interpreted by gcc if gdc is the compiler
2023-11-19 04:51:15 <ptrc> why does it pick gdc then .~.
2023-11-19 04:51:36 <ptrc> oh
2023-11-19 04:51:37 <ptrc> no
2023-11-19 04:51:38 <ptrc> i'm blind
2023-11-19 04:51:41 <ptrc> that's for manpages
2023-11-19 04:51:43 <ptrc> and not the tests
2023-11-19 04:52:39 <ptrc> wouldn't just --compiler=ldc2 and `-dw` in flags for tests solve it
2023-11-19 04:53:33 <celie> Probably why it doesn't choose ldc2 could be related to 2a1858868
2023-11-19 05:02:09 <celie> Hmm, it seems to compile fine with ldc2 without needing -dw/--dw
2023-11-19 05:03:22 <celie> and i looked at the CI logs when --compiler=gdc was used: "Error Failed to invoke the compiler gdc to determine the build platform: /bin/sh: gdc: not found"
2023-11-19 05:03:46 <celie> So, it seems 3.19 has a gdc while edge doesn't?
2023-11-19 05:04:42 <celie> Oh wait, edge has it in gcc-gdc
2023-11-19 05:12:14 <ptrc> meh, i've been trying to build it locally
2023-11-19 05:12:18 <ptrc> but i'd have to build ldc itself as well
2023-11-19 05:12:31 <ptrc> because until the builders finish the repository, they don't upload anything
2023-11-19 05:12:37 <ptrc> ( understandably so )
2023-11-19 05:18:13 <celie> What do you think of just using `bin/dub test --compiler=ldc2`, it seems to work on the CI without any DFLAGS
2023-11-19 05:20:03 <ptrc> imo that would be the preferred solution
2023-11-19 05:36:32 <celie> Ok, i have fixed up !55668, hopefully there are no more surprises when it builds on 3.19
2023-11-19 05:37:42 <celie> I think the problem is that gdc is available on 3.19 seemingly without an explicit depend on gcc-gdc
2023-11-19 05:38:29 <celie> I tested adding a depend on gcc-gdc in that MR, and `dub test` prefers gdc when that is available
2023-11-19 05:38:33 <ptrc> hm, let me see actually
2023-11-19 05:41:33 <ptrc> well
2023-11-19 05:42:00 <ptrc> the builder definitely has way more packages installed than just the standard stuff ( alpine-sdk, etc. )
2023-11-19 05:42:19 <ptrc> "682 MiB in 129 packages" vs "496 MiB in 96 packages" locally when i do `abuild deps` with 3.19 main
2023-11-19 05:42:52 <celie> and when using gdc, DFLAGS will be passed to that, which explains why we got confused when looking into `ldc2 --help` and `ldmd2 --help`
2023-11-19 05:45:09 <ptrc> alrighty
2023-11-19 05:45:12 <ptrc> hopefully it passes now :)
2023-11-19 05:47:44 <celie> Ok...so !55662 hasn't been merged yet
2023-11-19 05:48:52 <celie> algitbot: retry master
2023-11-19 05:49:22 <celie> hledger-stockquotes may very well be the last blocker for v3.19/community/x86_64
2023-11-19 05:50:28 <celie> Hmm, what would it take for the builder to try building dub first before hledger-stockquotes
2023-11-19 05:50:33 <celie> algitbot: retry master
2023-11-19 05:57:56 <ptrc> ...disabling hledger-stockquotes? :p
2023-11-19 05:58:20 <ptrc> but also
2023-11-19 05:58:21 <ptrc> 5839/5841
2023-11-19 05:58:21 <ptrc> yeah
2023-11-19 05:58:28 <ptrc> two left, so that would be the hledger and dub
2023-11-19 05:58:45 <celie> but there's already an MR updating hledger-stockquote's cabal.config
2023-11-19 05:58:50 <ptrc> oh?
2023-11-19 05:58:58 <celie> !55662
2023-11-19 05:59:22 <ptrc> wonder why it wasn't pushed directly to master
2023-11-19 05:59:42 <celie> CI pipeline is just waiting for s390x, which it is not enabled for anyway
2023-11-19 05:59:59 <ptrc> ah
2023-11-19 06:00:03 <ptrc> dotnet is blocking s390x
2023-11-19 06:00:07 <ptrc> and hm
2023-11-19 06:00:33 <ptrc> ikke: do we only have one s390x runner currently? i can't find the other one anywhere and the single one i can find has been stuck on dotnet for a while
2023-11-19 06:04:25 <celie> ^ and that's probably the last blocker for aarch64
2023-11-19 06:07:52 <celie> dub succeeded on x86_64, now hledger-stockquotes :)
2023-11-19 06:13:11 <celie> Ok, hledger-stockquotes succeeded on edge, hopefully no more surprises for 3.19
2023-11-19 06:27:38 <celie> algitbot: retry 3.18-stable
2023-11-19 06:31:10 <ptrc> \o/
2023-11-19 06:31:32 <celie> Yay, x86_64 3.19 is now uploading..
2023-11-19 06:31:44 <celie> community
2023-11-19 09:40:45 <ikke> algitbot: retry master
2023-11-19 09:40:54 <ikke> algitbot: retry 3.18-stable
2023-11-19 10:46:09 <andypost[m]> algitbot:rerty master
2023-11-19 10:46:22 <andypost[m]> algitbot: retry master
2023-11-19 16:18:44 <ikke> algitbot: retry master
2023-11-21 02:55:40 <celie> ptrc: Hi, just wondering if you're alright with moving quickjs to community in !55637
2023-11-21 02:55:56 <ptrc> oops, missed the ping; sure
2023-11-21 02:56:58 <celie> Thanks :)
2023-11-21 21:14:08 <ikke> omni: checksum failure ^
2023-11-21 21:35:07 <omni> ikke: saw, thanks, will look at now
2023-11-21 21:38:19 <omni> ah, of course, the patches are downloaded from that forge
2023-11-21 21:47:56 <ikke> yeah, patches from github and gitlab are unstable
2023-11-21 21:55:46 <omni> should I download and add 100K+ of patches to our repo?
2023-11-21 22:01:22 <omni> gotta go, unfortunately, but I opened !55874
2023-11-22 10:38:33 <andypost[m]> ikke: is aarch64 builder is hanging?
2023-11-22 10:40:13 <ikke> I'll check, but these qtwebengine builds (aka chromium) take a long time 
2023-11-22 10:41:34 <andypost[m]> thank you, arm* looks fine but 64 looks like hanging
2023-11-22 11:34:11 <ikke> andypost[m]: there are only so much copies of chromium that a server can build at the same time
2023-11-22 11:41:09 <ikke> andypost[m]: for the record, I think all of them are stuck / barely making progress
2023-11-22 11:48:34 <ikke> algitbot: retry master
2023-11-22 22:01:48 <ikke> algitbot: retry master
2023-11-23 22:27:37 <ptrc> omni: the `move to community` commits should've been `move from testing` :p
2023-11-23 22:29:19 <fluix> why is that the convention btw?
2023-11-24 00:58:58 <omni> ptrc: ugh.. yes.
2023-11-24 00:59:43 <omni> fluix: it's obvious where aports end up, so better to specify where they moved from
2023-11-24 01:02:55 <omni> fluix: and yes https://git.alpinelinux.org/aports/tree/COMMITSTYLE.md#n110
2023-11-24 01:41:41 <celie> algitbot: retry 3.14-stable
2023-11-24 01:42:31 <celie> (Just wondering why build-3-14-x86 seems to be stuck on fcgiwrap)
2023-11-24 01:46:54 <celie> algitbot: retry master
2023-11-24 01:49:53 <celie> Hmm, build-edge-x86_64's xapian-core error (1 test failed) isn't showing up in the "last error" column of build.alpinelinux.org
2023-11-24 02:16:24 <andypost[m]> algitbot: retry master
2023-11-24 02:16:47 <omni> celie: now
2023-11-24 02:18:51 <omni> successful on the 3.19 builder https://build.alpinelinux.org/buildlogs/build-3-19-x86_64/community/xapian-core/xapian-core-1.4.24-r0.log
2023-11-24 02:37:17 <celie> Ok, so the error has appeared in the column, but build-edge-x86_64 still seems to be slow to respond to the newly merged commits
2023-11-24 02:38:01 <celie> algitbot: retry master
2023-11-24 03:44:23 <omni> algitbot: retry 3-19
2023-11-24 03:44:28 <omni> algitbot: retry 3.19
2023-11-24 03:46:02 <omni> v3.19.0_rc1 or how does this work now before release?
2023-11-24 03:47:09 <omni> algitbot: retry master
2023-11-24 03:48:22 <celie> It's probably still master, as there is no 3.19-stable branch yet
2023-11-24 03:48:51 <omni> yes it was
2023-11-24 03:49:02 <celie> and it seems util-linux tests passed
2023-11-24 03:50:23 <celie> I hope flare completes soon son build-edge-x86_64 can upload its packages
2023-11-24 03:50:27 <celie> s/son/so/
2023-11-24 03:50:51 <omni> soon
2023-11-24 03:51:10 <celie> and now it's done :)
2023-11-24 03:51:31 <celie> Now onto testing/ ..
2023-11-24 03:52:26 <omni> *thumb roll*
2023-11-24 04:02:34 <fluix> omni: thanks. I knew it was from the commit style but I didn't realize both repositories end up in the commit message... which know seems obvious
2023-11-24 12:13:00 <omni> fail me once, shame on you, fail me twice, shame on me
2023-11-24 16:32:17 <ikke> algitbot: retry master
2023-11-24 21:15:32 <ikke> algitbot: retry 3.17-stable
2023-11-26 15:09:28 <celie> algitbot: retry 3.18-stable
2023-11-26 15:25:27 <celie> Probably it would be better to retry when llvm has finished building on edge (assuming the 3.18 and edge builders are hosted on the same machine), but let me give it one more try for now
2023-11-26 15:25:37 <celie> algitbot: retry 3.18-stable
2023-11-26 16:11:26 <ikke> celie: perl is a segfault
2023-11-26 16:12:10 <ikke> or, not sure if it's perl, but it's scudo_test
2023-11-26 16:16:41 <ikke> algitbot: retry 3.18-stable
2023-11-26 16:20:15 <ikke> algitbot: retry 3.17-stable
2023-11-26 17:53:45 <ikke> algitbot: retry master
2023-11-26 19:42:07 <ikke> algitbot: retry master
2023-11-26 20:59:48 <ikke> algitbot: retry master
2023-11-27 05:32:15 <ikke> algitbot: retry masterr
2023-11-27 05:32:16 <ikke> algitbot: retry master
2023-11-27 14:33:58 <omni> algitbot: retry master
2023-11-27 16:28:48 <ikke> algitbot: retry master
2023-11-28 01:04:39 <celie> ^ edbrowse on riscv64: i guess i should change the `want_check &&` to `if want_check` so prepare() doesn't fail when checks are disabled (as they are on the riscv64 builder), will try that shortly
2023-11-28 01:05:50 <celie> and the qt6 failed to build seem to be due to download errors, so..
2023-11-28 01:06:09 <celie> algitbot: retry master
2023-11-28 04:46:43 <celie> For edbrowse on riscv64: !56180
2023-11-28 04:48:36 <celie> algitbot: retry master
2023-11-28 06:13:41 <ikke> right, makes sense false && command fails with set -e
2023-11-28 06:33:11 <ajhalili2006> ---
2023-11-28 07:47:13 <realzNEO> is this channel just for keeping up with commits
2023-11-28 07:47:15 <realzNEO> or discussions too
2023-11-28 08:24:37 <ajhalili2006> realzNEO: guess you should go to #alpine-devel, it is more of commit logs and monitoring package builds
2023-11-28 11:45:40 <ikke> algitbot: retry master
2023-11-28 19:07:17 <celie> algitbot: retry master
2023-11-28 19:07:19 <celie> andypost[m]: hi, would it be possible to add a 3.19 milestone tag to !51536 so it gets more attention? thanks
2023-11-28 19:07:19 <celie> algitbot: retry master
2023-11-28 19:07:21 <celie> andypost[m]: thanks, so now i'll keep an eye on https://build.alpinelinux.org (and this channel) to see if anything errors out
2023-11-28 19:07:21 <celie> though i think the armhf builder is stuck on rakudo-star that was merged more than 12 hours ago
2023-11-28 19:07:23 <celie> algitbot: kick build-edge-armhf
2023-11-28 19:07:23 <celie> hmm, i wonder what's up with openldap on x86_64..
2023-11-28 19:07:25 <celie> algitbot: kick build-edge-x86_64
2023-11-28 19:07:25 <celie> algitbot: kick build-edge-x86_64
2023-11-28 19:07:27 <celie> algitbot: retry master
2023-11-28 19:07:27 <celie> algitbot: kick build-edge-armhf
2023-11-28 19:07:31 <celie> algitbot: kick build-edge-armhf
2023-11-28 19:07:31 <celie> algitbot: kick build-edge-armhf
2023-11-28 19:07:33 <celie> algitbot: kick build-3-19-s390x
2023-11-28 19:07:35 <celie> I wonder why those Python aports have started asking for typing-extensions now
2023-11-28 19:07:37 <celie> Exploring the typing-extensions thing in !53855
2023-11-28 19:07:37 <celie> I tried grepping for typing extensions in py3-apipkg source, but couldn't find it, so perhaps it's one of its dependencies that's asking for it..
2023-11-28 19:07:39 <celie> I think it works, so when you've confirmed it, i'll remove the commit with the test rebuild of py3-apipkg (or you can remove it too)
2023-11-28 19:07:39 <celie> Yes
2023-11-28 19:07:41 <celie> Great :)
2023-11-28 19:07:41 <celie> Ok, the last aport that you added typing-extensions to (py3-pytest-mock) also depends on setuptools_scm, so i guess that's the problem
2023-11-28 19:07:43 <celie> You're welcome
2023-11-28 19:07:43 <celie> I think omni found out about the ion-shell getrandom crate open64 issue in !50904, but found some other problem with it
2023-11-28 19:07:45 <celie> I think i encountered the py3-pyproject-api test failure while trying to upgrade it to 1.6.1
2023-11-28 19:07:45 <celie> I'm not sure, but i just tried the ion-shell that's currently in the repo, and i didn't get a syntax error
2023-11-28 19:07:51 <celie> Hmm, seems like lfs64 errors in tinyxml2
2023-11-28 19:07:53 <celie> Checksum failed
2023-11-28 19:07:53 <celie> Anyway, last MR before i head off for the night: !53860
2023-11-28 19:07:59 <celie> My MR should fix the open64 errors and another 2 errors i encountered due to `cargo test` trying to download crates that `cargo fetch` did not download (probably due to --target)
2023-11-28 19:07:59 <celie> I think omni should handle the upgrade, especially because upstream doesn't seem to be tagging releases for the past few years
2023-11-28 19:08:01 <celie> It seems htmlq also needs a checksum update for the patch
2023-11-28 19:08:01 <celie> I tried the ion binary from build artifacts and i don't seem to get the syntax error omni mentioned in !50904
2023-11-28 19:08:03 <celie> algitbot: retry master
2023-11-28 19:08:03 <celie> algitbot: retry master
2023-11-28 19:08:05 <celie> I just had a thought, could `make -j1 test` solve #15388 ?
2023-11-28 19:08:05 <celie> For py3-lz4: !53893
2023-11-28 19:08:07 <celie> For navi: !53897
2023-11-28 19:08:13 <celie> For py3-snuggs: !53908 (patch is from Debian)
2023-11-28 19:08:15 <celie> For nlohmann-json: !53912
2023-11-28 19:08:17 <celie> I wonder if 'kick' still works..
2023-11-28 19:08:19 <celie> There seems to be a lot of "failed to mkdir" errors (for example, libhandy1 and gtksourceview4)
2023-11-28 19:08:19 <celie> https://build.alpinelinux.org/buildlogs/build-3-19-s390x/community/timed/timed-3.6.14-r0.log - setcap binary found, i wonder if it's new
2023-11-28 19:08:21 <celie> Hmm, and both of them are trying to mkdir ~/.config/ibus/bus (while running tests)
2023-11-28 19:08:21 <celie> https://build.alpinelinux.org/buildlogs/build-3-19-aarch64/community/uhttpmock/uhttpmock-0.9.0-r0.log is trying to mkdir ~/.config/glib-2.0/settings in tests
2023-11-28 19:08:23 <celie> Anyway, i opened !53941 to !53944 to fix the build issues i could help out with
2023-11-28 19:08:23 <celie> https://build.alpinelinux.org/buildlogs/build-3-19-x86_64/community/gops/gops-0.3.28-r2.log is trying to mkdir ~/.config/gops
2023-11-28 19:08:27 <celie> Ok
2023-11-28 19:08:29 <celie> Anyway, a few more MRs to fix issues found by the 3.19 builders: !53943 !53942 !53897
2023-11-28 19:08:29 <celie> For mutter: !53961
2023-11-28 19:08:31 <celie> I don't remember that happening on the CI though
2023-11-28 19:08:31 <celie> OCaml is failing on s390x due to "No file descriptors available" and "diff: unrecognized option: strip-trailing-cr"
2023-11-28 19:08:33 <celie> and OCaml built successfully on build-3-19-ppc64le, so perhaps a retry will fix it
2023-11-28 19:08:33 <celie> It seems it didn't happen on edge too, and OCaml was rebuilt there last month
2023-11-28 19:08:35 <celie> For gitstatus: !53968
2023-11-28 19:08:35 <celie> algitbot: retry master
2023-11-28 19:08:37 <celie> For gnome-feeds: !53973
2023-11-28 19:08:37 <celie> For py3-validate-pyproject: !53970
2023-11-28 19:08:39 <celie> Alright, last fix of the day from me for errors found by the 3.19 builders: !53980
2023-11-28 19:08:39 <celie> For libselinux: !53974
2023-11-28 19:08:49 <celie> !54035 upstream changed repository name, but i think i'll let @mpolanski do the actual package transition
2023-11-28 19:08:51 <celie> Other merge requests that fix issues found by the 3.19 builders: !54029 !54033 !54030 !54037
2023-11-28 19:08:53 <celie> More fixes: !54039 !54041 !54042 !54043 !54045
2023-11-28 19:08:59 <celie> Fixes for errors from the 3.19 builders: !54075 !54076 !54077 !54080 !54081 !54082 !54083
2023-11-28 19:09:01 <celie> 2 fixes from earlier today: !54039 !54041
2023-11-28 19:09:01 <celie> andypost[m]: Thanks :)
2023-11-28 19:09:05 <celie> s/3.18/3.19/
2023-11-28 19:09:05 <celie> Fixes for issues found during the 3.18 rebuild: !54120 !54130 !54132 !54134
2023-11-28 19:09:07 <celie> Opps, sorry, !54129 not 54120
2023-11-28 19:09:07 <celie> Fixes for the 3.19 build issues: !54208 !54209 !54213 !54215 !54216 !54217
2023-11-28 19:09:41 <celie> taskd's old url now returns 404, according to https://taskwarrior.org/download/ the files are now hosted on Github: !54307 (no checksum change)
2023-11-28 19:09:41 <celie> ansible-lint's checksum changed: !54327
2023-11-28 19:09:43 <celie> This should allow oq to pass checks on 3.19: !54352
2023-11-28 19:09:51 <celie> Fixes for errors found by the 3.19 rebuilders: !54378 !54380 !54381
2023-11-28 19:09:53 <celie> More fixes: !54385, and possibly !54383
2023-11-28 19:09:53 <celie> There's also !54378 from earlier on, which as rustup is not enabled for s390x, probably doesn't need to wait for the s390x runner
2023-11-28 19:09:55 <celie> Perhaps checkapk should also list the packages it thinks needs rebuilding, maybe if there are too many, it could output them to a file that's added to the CI build artifacts
2023-11-28 19:09:55 <celie> I kind of brought up the possibility of that happening (non-library dependencies being caught) in https://gitlab.alpinelinux.org/alpine/abuild/-/merge_requests/223#note_339534 though i probably didn't choose a very good example, as the Python aports will have to be rebuilt for major version upgrades, but due to the site-packages directory change, not due to linking to Python libraries
2023-11-28 19:09:59 <celie> Umm, ikke, i don't think the pipeline passed for !54269: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/54269/pipelines
2023-11-28 19:10:01 <celie> Seems like it's just copying udev rules, so should be alright
2023-11-28 19:10:01 <celie> Hmm, game-devices-udev fails checksum, hopefully nothing else fails after that's fixed
2023-11-28 19:10:03 <celie> However, i still see quite a number of errors, but they don't cause the build to fail
2023-11-28 19:10:03 <celie> freedoom seems to build fine after this applying patch: https://github.com/freedoom/freedoom/commit/d64ddc6ea
2023-11-28 19:10:05 <celie> to generate the PDF manual
2023-11-28 19:10:05 <celie> Because it couldn't run asciidoctor-pdf
2023-11-28 22:43:05 <ikke> algitbot: retry master
2023-11-29 09:44:47 <omni> I had missed to run !56037 riscv64 pipeline
2023-11-29 09:45:03 <omni> !56265
2023-11-29 11:26:28 <ikke> Those unknown relocations on rv64 are anoying
2023-11-29 13:16:48 <andypost[m]> algitbot: retry master
2023-11-29 14:17:26 <andypost[m]> algitbot: retry master
2023-11-29 19:50:39 <andypost[m]> algitbot: retry master
2023-11-30 01:03:17 <celie> algitbot: retry master
2023-11-30 01:52:35 <celie> It seems that worked to unblock the builders :)
2023-11-30 18:18:15 <ptrc> sigh