2024-05-01 00:21:56 <omni> algitbot: retry master
2024-05-01 00:27:03 <celie> I wonder if we should get maintainers involved in fixing the build failures
2024-05-01 00:33:09 <omni> not a bad idea
2024-05-01 00:33:43 <omni> they may also be better at fixing the issues and should probably be posted anyway
2024-05-01 00:33:43 <cely> Hi, omni
2024-05-01 00:33:47 <omni> hi
2024-05-01 00:34:09 <cely> Hmm, it's May already (noticed while checking lots on irclogs.a.o)
2024-05-01 00:34:14 <cely> s/lots/logs/
2024-05-01 00:35:36 <omni> it is
2024-05-01 00:35:53 <cely> and this is the first channel with a *-2024-05.log file :)
2024-05-01 00:40:49 <cely> I noticed py3-meson-python has no Maintainer
2024-05-01 00:42:54 <cely> Hahaha
2024-05-01 00:43:26 <cely> "FileNotFoundError: [Errno 2] No such file or directory: 'crap'"
2024-05-01 00:43:31 <cely> When building py3-meson-python
2024-05-01 00:43:38 <omni> nice
2024-05-01 00:44:39 <cely> Apparently, lots of tests there require Git (tried it out in a container without that installed, and got a lot more errors than what i saw on build.a.o)
2024-05-01 00:48:09 <omni> speaking of crap, my fan spun up when I clicked the search thing in the crappy github web ui crap
2024-05-01 00:48:31 <omni> they have really bloated that web page
2024-05-01 00:49:43 <omni> it took a while to get to input some letters in the search box
2024-05-01 00:50:20 <cely> They're probably sending your search query to an AI
2024-05-01 00:50:47 <omni> that shouldn't spin my fan up
2024-05-01 00:51:04 <omni> that tab was suddenly taking all of my system resources
2024-05-01 00:51:31 <cely> Qutebrowser?
2024-05-01 00:53:02 <omni> yes, with qt5-qtwebengine because qt6-qtwebengine is worse
2024-05-01 00:59:49 <cely> algitbot: retry master
2024-05-01 01:06:35 <cely> Hmm....
2024-05-01 01:06:48 <cely> tracker was upgraded to 3.7.1 but tracker-miners stayed at 3.6.2
2024-05-01 01:06:51 <cely> No wonder it is failing
2024-05-01 01:41:31 <cely> algitbot: retry master
2024-05-01 01:43:52 <cely> algitbot: retry master
2024-05-01 01:46:22 <cely> algitbot: retry master
2024-05-01 01:46:51 <cely> algitbot: retry master
2024-05-01 01:46:59 <cely> algitbot: retry master
2024-05-01 01:51:43 <cely> algitbot: retry master
2024-05-01 01:52:23 <cely> algitbot: retry master
2024-05-01 01:54:05 <cely> algitbot: retry master
2024-05-01 01:55:04 <cely> algitbot: retry master
2024-05-01 02:39:41 <cely> algitbot: retry master
2024-05-01 03:34:44 <cely> algitbot: retry master
2024-05-01 03:43:28 <cely> 31 aports left for s390x community, 36 for armhf, 80 for armv7, and 126 for aarch64
2024-05-01 03:54:42 <cely> I hope x86 isn't stuck on google-cloud-cpp
2024-05-01 03:57:04 <cely> jellyfin: "The specified RuntimeIdentifier 'alpine.3.20.0-arm' is not recognized"
2024-05-01 04:03:45 <cely> 25 aports left for s390x community, 35 for armhf, 78 for armv7, and 118 for aarch64
2024-05-01 04:21:06 <cely> Ok, x86 has moved on now, so it isn't stuck
2024-05-01 04:40:43 <cely> I wonder if we'll be able to see <100 packages for aarch64 by the end of the day
2024-05-01 05:29:27 <cely> 22 aports left for s390x community, 28 for armhf, 71 for armv7, and 103 for aarch64
2024-05-01 05:46:03 <cely> 100 aports to go for aarch64!
2024-05-01 05:49:33 <ikke> bootstrapping openjdk17 for aarch64
2024-05-01 21:03:56 <omni> algitbot: retry master
2024-05-01 21:04:41 <omni> algitbot: retry master
2024-05-02 04:00:56 <cely> Last 10 aports for s390x community!!
2024-05-02 04:20:48 <cely> I wonder if spotifyd will be fixed by https://github.com/Spotifyd/spotifyd/pull/1220 (it removes the rustc-serialize that's failing, but that's just the side effect of doing some other changes, that look quite major)
2024-05-02 04:51:54 <cely> ^ with that, the aports left for s390x community is now in the single-digit
2024-05-02 04:52:06 <cely> that = gifski, not the tpm2 thing..
2024-05-02 04:57:27 <cely> Time to enumerate the failing aports for s390x
2024-05-02 04:58:38 <cely> 1. git-interactive-rebase-tool 2. gpick 3. java-lz4 4. kaidan 5. libsurvive 6. massif-visualizer 7. plasma-dialer 8. tpm2-abrmd 9. tpm2-tss-engine
2024-05-02 05:02:40 <cely> AUR's libsurvive-git package mentions the sciplot error that we're also having, same thing with AUR's gpick-git that mentions the boost error we're having
2024-05-02 05:02:51 <cely> Doesn't look like they were fixed though
2024-05-02 05:04:47 <cely> The tpm2 aports have !64820
2024-05-02 07:15:36 <cely> kaidan and plasma-dialer seem to require version 5 of Kirigami Addons, but i can't seem to find that in aports anymore
2024-05-02 07:16:22 <cely> massif-visualizer on the other hand, requires version 5 of KCharts that is available in kdiagram5
2024-05-02 07:17:34 <cely> If i am right about kdiagram5, then !65239 should fix massif-visualizer
2024-05-02 07:17:45 <cely> Don't know what to do about kaidan and plasma-dialer though
2024-05-02 07:18:58 <cely> So, out of the 9 failing aports on s390x, i think these are left: gpick, java-lz4, kaidan, libsurvive, plasma-dialer
2024-05-02 07:23:06 <cely> !64820 should also fix gnome-remote-desktop
2024-05-02 12:55:52 <cely> Grrrrrrrrrr
2024-05-02 12:56:17 <cely> When i saw the pytest upgrade, i wondered if it woulc cause some trouble
2024-05-02 12:56:20 <cely> and it has
2024-05-02 12:56:25 <cely> s/woulc/would/
2024-05-02 12:56:29 <ikke> :(
2024-05-02 12:56:39 <cely> <-- so annoyed by python breaking changes that i can't spell
2024-05-02 12:56:50 <cely> Never mind, we have py3-pytest7
2024-05-02 12:58:49 <ikke> :)
2024-05-02 13:04:54 <cely> Now, two more aports are failing with pytest 8.2.0
2024-05-02 13:05:31 <cely> Don't think i can switch so many aports to pytest7, these 2 are affected by https://github.com/pytest-dev/pytest/issues/12263
2024-05-02 13:06:17 <cely> so, i will try adding this patch: https://github.com/tornadoweb/tornado/pull/3374
2024-05-02 13:13:20 <cely> It seems to work
2024-05-02 15:07:54 <cely> In other news, FreeBSD has reverted Pytest 8.2.0
2024-05-02 15:24:35 <cely> ^ pcc-libs (pcc.ludd.ltu.se (130.240.207.127:80): Host is unreachable)
2024-05-02 19:17:52 <omni> algitbot: retry master
2024-05-02 19:18:16 <ikke> ftr, I'm bootstrapping on x86_64
2024-05-02 21:45:18 <andypost[m]> algitbot: retry master
2024-05-02 21:46:12 <andypost[m]> algitbot: retry master
2024-05-02 21:49:34 <andypost[m]> algitbot: retry master
2024-05-03 00:01:38 <celie> Has pytest 8.2.0 or rust 1.78.0 cause anything to go up in flames?
2024-05-03 00:01:45 <celie> caused*
2024-05-03 00:02:03 <celie> From a brief scroll through the backlog it seems the answer is no
2024-05-03 00:02:29 <celie> There was only mopidy that failed due to pytest 8.2.0, but i've already covered that with the py3-tornado patch i imported
2024-05-03 00:03:35 <celie> Which is also a reminder that maybe CI should be run for Python aport MRs that were created before pytest 8.2.0 was merged (and so didn't run CI with that)
2024-05-03 00:10:59 <ptrc> tbf i expected the pytest upgrade to be more breaking than rust
2024-05-03 00:11:08 <ptrc> also, hm, you're right
2024-05-03 00:11:30 <ptrc> i guess anything that had its last CI run more than a *while* ago should be retried
2024-05-03 00:11:49 <celie> FreeBSD has already reverted pytest 8.2.0
2024-05-03 00:19:54 <celie> algitbot: retry master
2024-05-03 00:40:19 <celie> algitbot: retry master
2024-05-03 00:42:47 <celie> algitbot: retry master
2024-05-03 00:58:06 <celie> ^ rnp: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064486 (mentions the same tests that fail once py3-setuptools has been added to makedepends)
2024-05-03 00:58:16 <celie> No fix though
2024-05-03 01:19:04 <celie> algitbot: retry master
2024-05-03 01:20:19 <celie> I think libsurvive is not compatible with sciplot 0.3.x
2024-05-03 01:25:50 <celie> algitbot: retry master
2024-05-03 01:26:11 <celie> algitbot: retry master
2024-05-03 01:32:40 <celie> algitbot: retry master
2024-05-03 04:49:52 <cely> algitbot: retry master
2024-05-03 04:50:27 <cely> algitbot: retry master
2024-05-03 04:50:49 <cely> Flaky tests :/
2024-05-03 04:52:39 <cely> and the worst thing is, not only is it flaky, if it fails, it outputs a huge log file
2024-05-03 04:53:56 <cely> algitbot: retry master
2024-05-03 04:55:42 <cely> which may be one argument for not using the community/starship method of automatically re-running the tests if it fails
2024-05-03 04:56:14 <cely> (we do not want to keep the huge log from the failed runs)
2024-05-03 05:01:07 <cely> Ouch, armv7 is building erlang and sbcl at the same time
2024-05-03 05:03:32 <cely> I wonder how much faster sbcl would build if it was built by itself
2024-05-03 05:03:52 <cely> (now it's built by ecl)
2024-05-03 05:18:29 <ikke> FindKChart.cmake not  found ^
2024-05-03 05:20:26 <cely> I have an MR for that
2024-05-03 05:20:30 <cely> The KChart thing
2024-05-03 05:21:12 <cely> It's the kaidan and plasma-dialer failure that is worrying
2024-05-03 05:21:39 <cely> because Kirigami Addons seem to be available only for KDE6 now
2024-05-03 05:22:14 <cely> ^ !65239
2024-05-03 05:23:46 <cely> ^ gpick probably isn't compatible with boost1.84
2024-05-03 05:26:31 <ikke> Similar error reported for boost 1.72: https://github.com/thezbyg/gpick/issues/182
2024-05-03 05:32:54 <ikke> algitbot: retry master
2024-05-03 07:37:56 <cely> algitbot: retry master
2024-05-03 07:43:10 <cely> algitbot: retry master
2024-05-03 08:22:27 <cely> Now x86 has reached less than 200 aports left for 3.20 community :)
2024-05-03 13:59:16 <cely> ansible-lint checksums has changed yet again
2024-05-03 17:43:34 <cely> algitbot: retry master
2024-05-03 18:00:12 <cely> algitbot: retry master
2024-05-03 23:47:39 <celie> algitbot: retry master
2024-05-04 00:05:53 <celie> algitbot: retry master
2024-05-04 00:23:48 <cely> algitbot: retry master
2024-05-04 00:33:30 <cely> algitbot: retry master
2024-05-04 02:36:39 <cely> I have a feeling build-3-20-aarch64 may reach 25 aports today
2024-05-04 02:36:49 <cely> aports left*
2024-05-04 02:37:16 <cely> and build-3-20-x86 could probably be much lower too if it wasn't stuck on py3-tqdm
2024-05-04 02:37:51 <cely> With riscv64 and x86_64 probably being stuck too
2024-05-04 02:38:26 <cely> i think ppc64le will be the next arch to reach less than 500 aports left
2024-05-04 02:38:42 <cely> and from there hopefully on to less than 100 :)
2024-05-04 04:42:54 <cely> So, the latest status is: 10 aports left for s390x community, 12 for armhf, 18 for armv7, 24 for aarch64, 79 for x86 (stuck), and 709 for ppc64le
2024-05-04 04:47:21 <cely> I'm quite sure s390x was at 8 or 9 aports left about 2 days ago
2024-05-04 04:47:27 <cely> I wonder how the number went back up to 10
2024-05-04 04:48:06 <cely> Did a new failing aport get added? or more likely, that new aport added to the queue depends on one of the failing aports..
2024-05-04 06:30:02 <cely> Uh oh, ppc64le is building keycloak-config-cli again (iirc, the last time it got stuck on this)
2024-05-04 11:32:26 <omni> oh?
2024-05-04 11:37:33 <omni> commented in !65329
2024-05-04 12:28:50 <cely> algitbot: retry master
2024-05-04 12:29:43 <cely> Seems to work
2024-05-04 12:30:40 <cely> algitbot: retry master
2024-05-04 13:14:49 <cely> algitbot: retry master
2024-05-04 14:31:02 <cely> algitbot: retry master
2024-05-04 14:34:02 <cely> algitbot: retry master
2024-05-04 14:36:07 <cely> Latest on the aports left for 3.20 community: 10 for s390x, 13 for armhf, 23 for armv7, 24 for aarch64, 34 for x86, 273 for ppc64le
2024-05-04 14:37:32 <cely> Hmm, x86 is back to 35, due to the py3-pytest-async upgrade needed for pytest 8.2.0 compatibility
2024-05-04 14:38:04 <cely> but that's probably not going to fail, and will be reached eventually with enough retries
2024-05-04 14:57:44 <fossdd> the black issue is due to pytest 8.2.0
2024-05-04 14:57:46 <fossdd> https://github.com/pytest-dev/pytest/issues/12278
2024-05-04 14:58:01 <fossdd> maybe the pytest upgrade should be reverted?
2024-05-04 14:58:23 <cely> The file descriptor not availble error is also due to pytest 8.2.0?
2024-05-04 14:58:36 <fossdd> yes
2024-05-04 14:59:15 <cely> Pytest has @fab as maintainer, maybe you should take maintainership so you can make such decisions (whether an upgrade should be reverted or not)
2024-05-04 14:59:38 <ikke> fab is not really active and does not mind transferring maintainership
2024-05-04 15:00:05 <fossdd> alright i'll do an MR
2024-05-04 15:01:19 <cely> Anyway, i've already made a few pytest 8.2.0 compatibility commits, so will probably need to make sure the revert doesn't break those instead
2024-05-04 15:02:41 <cely> I think py3-tornado and py3-pytest-asyncio are 2 aports that i patched and upgraded for pytest 8.2.0 compatibility
2024-05-04 15:03:59 <cely> I think black has passed on build-edge-x86 though
2024-05-04 15:04:45 <ikke> Race condition?
2024-05-04 15:05:09 <fossdd> yes
2024-05-04 16:17:27 <cely> Firefox has failed :O
2024-05-04 16:24:40 <cely> So, firefox-esr was built on edge with Rust 1.77
2024-05-04 16:25:58 <cely> algitbot: retry master
2024-05-04 16:26:41 <cely> algitbot: retry master
2024-05-04 17:16:04 <cely> algitbot: retry master
2024-05-04 18:55:18 <andypost[m]> algitbot: retry master
2024-05-04 19:45:21 <ikke> bootstrapping openjdk11 on x86_64
2024-05-04 20:17:42 <ikke> done
2024-05-04 20:17:50 <ikke> algitbot: retry master
2024-05-04 21:55:53 <andypost[m]> algitbot: retry master
2024-05-05 00:53:58 <cely> algitbot: retry master
2024-05-05 04:06:30 <cely> x86_64 finally reached <1000 aports
2024-05-05 06:30:24 <cely> So, 6 architectures have reached 20 aports and below for 3.20 community :)
2024-05-05 06:30:46 <cely> Hopefully, x86_64 will join them soon..
2024-05-05 06:32:14 <ikke> I'm a bit worried about rv64 though
2024-05-05 11:46:01 <omni> why did s390x start rebuilding ceph17 before building apache-arrow 16.0.0?
2024-05-05 11:47:17 <ikke> possibly: 1. Dependency cycle. 2. Dependecy in subpackage that cannot be detected
2024-05-05 11:49:39 <omni> ikke: could it be sorted manually so that we don't need to rebuild ceph17 again?
2024-05-05 11:50:14 <omni> like as in aborting the ceph17 build on s390x
2024-05-05 11:51:09 <omni> seems like it did the correct order on build-3-20-s390x
2024-05-05 11:51:16 <ikke> ^
2024-05-05 11:51:23 <omni> thanks
2024-05-05 11:52:15 <omni> thank you very much even =)
2024-05-05 11:52:24 <omni> ceph takes such a long time to build
2024-05-05 11:52:35 <omni> now I'll afk for a bit
2024-05-05 11:53:10 <ikke> now it does build apache-arrow first
2024-05-05 11:54:13 <omni> I hope they will have the correct order on the 3-20 builders where it hasn't started yet
2024-05-05 11:55:18 <ikke> ap builddirs does seem to indicate the correct order
2024-05-05 11:55:30 <omni> perhaps we could help out keeping watch to see that apache-arrow 16 has been built when any starts building cep17 or ceph18
2024-05-05 11:56:14 <omni> now afk
2024-05-05 15:46:45 <cely> Nice, 6 architectures are now at <15 aports left
2024-05-05 16:11:03 <cely> Hmm, it seems s390x just has 3 failing aports left
2024-05-05 16:11:19 <cely> They should be: 1. gpick 2. homer-app 3. java-lz4
2024-05-05 16:51:44 <cely> algitbot: retry master
2024-05-05 16:51:54 <ikke> homer-app should be a simple fix, not?
2024-05-05 23:35:41 <celie> algitbot: retry master
2024-05-05 23:36:24 <celie> I think ezstream passed on other archs
2024-05-05 23:36:28 <celie> algitbot: retry master
2024-05-06 00:10:32 <celie> algitbot: retry master
2024-05-06 01:25:28 <celie> algitbot: retry master
2024-05-06 01:26:17 <celie> algitbot: retry master
2024-05-06 01:28:44 <celie> algitbot: retry master
2024-05-06 01:29:08 <celie> algitbot: retry master
2024-05-06 01:35:35 <cely> algitbot: retry master
2024-05-06 01:36:29 <cely> algitbot: retry master
2024-05-06 03:41:07 <cely> lol
2024-05-06 03:41:41 <cely> My connection is finally a bit better (still slow though, just not very slow)
2024-05-06 03:42:15 <cely> but good enough that i can finally see the "Merging, drum roll please" message in Gitlab
2024-05-06 03:49:52 <cely> To the 4 aports left in armhf, i think armv7 and ppc64le add 2 more (to make it 6), and aarch64 and x86 add 3 more on top of that (so 9)
2024-05-06 03:52:00 <cely> rkward is failing on aarch64, armv7, and x86; while ezstream seems to fail only on aarch64
2024-05-06 03:52:08 <cely> I'll try to see if i can find the others
2024-05-06 03:56:11 <cely> It seems Rust 1.78 broke ncspot, so that affects ppc64le but not x86 and the ARMs
2024-05-06 03:56:27 <cely> I mean, ppc64le is the one trying to build it with 1.78, the other 4 built it with 1.77
2024-05-06 03:57:12 <cely> neo4j is only enabled for aarch64 and x86_64
2024-05-06 03:57:42 <cely> and jellyfin only for aarch64, armv7, and x86_64
2024-05-06 04:02:10 <cely> cargo-edit tests segfault on x86, but seem ok on the others (it's not Rust 1.78 this time, as the others used that too)
2024-05-06 04:03:33 <cely> ppc-libs is only enabled for x86 and x86_64
2024-05-06 04:16:21 <cely> I wonder if aws-c-io and libei tests may be failing on riscv64 due to them timing out
2024-05-06 04:23:48 <cely> aarch64 adds to armv7's jellyfin and rkward: ezstream, neo4j, and very likely, jellyfin-web (as this depends on jellyfin, and is disabled for armv7)
2024-05-06 13:14:04 <cely> I wonder if we should just switch pcc-libs (and pcc) to distfiles
2024-05-06 13:14:29 <cely> but i think it would have to be distfiles.a.o/distfiles/v3.19, as they don't seem to be available in edge
2024-05-06 14:54:34 <celie> algitbot: retry master
2024-05-06 14:55:53 <celie> algitbot: retry master
2024-05-06 15:13:39 <celie> algitbot: retry master
2024-05-06 15:44:27 <fossdd> test
2024-05-06 15:46:02 <ikke> test failed
2024-05-06 19:43:15 <omni> downterm
2024-05-07 00:10:49 <celie> algitbot: retry master
2024-05-07 00:14:30 <celie> algitbot: retry master
2024-05-07 00:25:15 <celie> algitbot: retry master
2024-05-07 00:31:09 <celie> algitbot: retry master
2024-05-07 00:51:15 <cely> Hmm, is redict also affected by #16056? but how did valkey solve it..seems like it just passed after enough retries?
2024-05-07 00:51:27 <cely> algitbot: retry master
2024-05-07 04:30:01 <cely> I think pg_probackup needs to be disabled for the same archs as postgresql15
2024-05-07 05:31:49 <cely> Time sensitive tests?
2024-05-07 05:31:50 <cely> algitbot: retry master
2024-05-07 06:06:16 <cely> algitbot: retry master
2024-05-07 07:13:10 <cely> algitbot: retry master
2024-05-07 11:29:12 <ikke> helix: https://github.com/helix-editor/helix/commit/0546273570710b97e9eebfff84298afbbb372f02
2024-05-07 15:14:50 <cely> algitbot: retry master
2024-05-07 15:17:00 <cely> algitbot: retry master
2024-05-07 15:18:45 <cely> algitbot: retry master
2024-05-07 15:26:32 <cely> algitbot: retry master
2024-05-07 15:48:20 <cely> algitbot: retry master
2024-05-07 16:00:32 <cely> algitbot: retry master
2024-05-07 16:02:29 <cely> algitbot: retry master
2024-05-07 16:04:32 <cely> algitbot: retry master
2024-05-07 16:06:55 <cely> algitbot: retry master
2024-05-07 16:08:41 <cely> algitbot: retry master
2024-05-07 16:09:46 <cely> I think ppc64le only has rnp and virt-manager left that are failing
2024-05-07 16:10:15 <cely> algitbot: retry master
2024-05-07 16:11:31 <cely> algitbot: retry master
2024-05-07 16:11:49 <cely> Same with armhf
2024-05-07 16:12:46 <cely> armv7 additionally has jellyfin and rkward
2024-05-07 16:12:59 <cely> algitbot: retry master
2024-05-07 16:14:52 <cely> algitbot: retry master
2024-05-07 16:15:42 <cely> algitbot: retry master
2024-05-07 16:17:41 <cely> algitbot: retry master
2024-05-07 16:18:55 <cely> algitbot: retry master
2024-05-07 16:20:05 <cely> and aarch64 adds ezstream, jellyfin-web, and neo4j
2024-05-07 16:21:19 <cely> Hmm, 584 aports left for x86_64
2024-05-07 16:25:20 <cely> and 1962 for riscv64
2024-05-07 16:27:41 <cely> algitbot: retry master
2024-05-07 16:29:20 <cely> As for x86, it should be: cargo-edit, pcc, pcc-libs, rkward, rnp, virt-manager
2024-05-08 01:56:39 <celie> algitbot: retry master
2024-05-08 02:00:30 <celie> algitbot: retry master
2024-05-08 02:14:33 <celie> algitbot: retry master
2024-05-08 04:21:58 <cely> algitbot: retry master
2024-05-08 10:32:46 <andypost[m]> algitbot: retry 3-19-stable
2024-05-08 10:33:01 <andypost[m]> algitbot: retry 3.19-stable
2024-05-08 16:07:02 <celie> algitbot: retry master
2024-05-08 21:39:47 <omni> fitting name, code blocks
2024-05-09 01:41:37 <celie> Codeblocks is still blocking the builders :(
2024-05-09 01:42:00 <celie> Probably it should be renamed Builderblocks
2024-05-09 01:44:39 <celie> I'm thinking of just disabling it, with the reason that 13 volatile patches is too many, and a request to re-enable it can be made when that has been reduced to a manageable number (like 3), probably by merging all the small patches
2024-05-09 01:45:45 <andypost[s]> celie: ++ just file issue to unblock someday
2024-05-09 01:46:09 <celie> Not sure i get what you mean
2024-05-09 01:46:19 <celie> You mean disable it and file an issue?
2024-05-09 01:46:55 <andypost[s]> yes, usually disabled packages has ref to issue to enable
2024-05-09 02:30:56 <cely> #16098
2024-05-09 11:11:05 <cely> So, only "A" works?
2024-05-09 11:11:14 <cely> Cpr 200
2024-05-09 11:11:41 <cely> Cissue 300
2024-05-09 11:12:10 <cely> Tissue 404
2024-05-09 11:12:52 <cely> Zissue 404
2024-05-09 11:13:06 <cely> Cissue 403
2024-05-09 11:13:22 <cely> Cissue 404
2024-05-09 11:13:25 <cely> Cissue 405
2024-05-09 11:13:34 <cely> I think 404 just went 404
2024-05-09 11:14:09 <cely> Tissue 1234
2024-05-09 13:20:35 <cely> x86_64 has less than 400 aports left for 3.20 community
2024-05-09 13:21:00 <ikke> Wonder if rv64 will make it
2024-05-09 13:23:30 <cely> Maybe with more (failing) aports disabled, it will make it
2024-05-09 14:02:02 <cely> x86_64 is building Deno again
2024-05-09 14:02:03 <cely> Let's hope it gets through this time
2024-05-09 16:42:21 <cely> Deno fails again :(
2024-05-09 16:42:31 <cely> This is the 3rd time, i think
2024-05-09 16:43:05 <ikke> We should make an issue for jirutka
2024-05-09 16:45:18 <cely> I wonder if an upgrade will solve it, i saw Deno 1.43.2, but didn't feel up to making an MR for that, as the APKBUILD is rather involved
2024-05-09 16:46:09 <cely> Hopefully the new version works with Rust 1.78, or it'd open another can of worms (aarch64 has already built Deno successfully..but with Rust 1.77)
2024-05-09 16:52:53 <nmeum> should we just open an issue and disable it for now?
2024-05-09 16:53:16 <ikke> algitbot: retry master
2024-05-09 16:54:26 <cely> ^ pcc-libs source website cannot be reached
2024-05-09 16:54:53 <ikke> easy fix is to copy the source on distfiles to v3.20
2024-05-09 16:55:14 <cely> but from v3.19
2024-05-09 16:55:20 <cely> I think i checked edge, and they weren't there
2024-05-09 16:55:37 <ikke> indeed
2024-05-09 16:55:55 <ikke> done
2024-05-09 16:56:23 <cely> Probably pcc needs the same thing done too
2024-05-09 16:57:48 <ikke> done
2024-05-09 16:58:08 <cely> Thanks :)
2024-05-09 16:59:05 <nmeum> rnp should be fixed by !65414 still awaiting a review from jirutka
2024-05-09 17:00:14 <cely> and virt-manager has #15924 with link to upstream issue
2024-05-09 17:00:38 <cely> (upstream has determined the issue is not caused by pytest 8, bit by new libvirt)
2024-05-09 17:00:45 <cely> s/bit/but/
2024-05-09 17:02:01 <cely> rnp and virt-manager should be the last blockers for armhf
2024-05-09 17:02:50 <cely> armv7 additionally has jellyfin and rkward
2024-05-09 23:49:38 <andypost[m]> algitbot: retry master
2024-05-10 00:17:25 <andypost[m]> algitbot: retry master
2024-05-10 01:45:43 <cely> algitbot: retry master
2024-05-10 02:16:46 <cely> So, netpbm failed, followed almost immediately by openjdk21 (on build-3-20-x86_64)
2024-05-10 02:17:23 <cely> I saw netpbm on build.a.o, but missed seeing it in the "last error" column, and thought it had succeeded, apparently not
2024-05-10 03:37:49 <cely> build-3-20-x86_64 now has less than 300 aports to go
2024-05-10 03:38:00 <cely> Hopefully that will be 200 aports by the end of the day
2024-05-10 13:38:47 <omni> oh-no, I got the wrong date in that and the correct one is earlier
2024-05-10 13:47:47 <cely> What date?
2024-05-10 14:47:13 <cely> Hmm, today seems like a quiet day commits-wise
2024-05-10 14:50:00 <cely> build-3-20-x86_64 keeps trying (and failing) to build ghc
2024-05-10 15:02:03 <cely> algitbot: retry master
2024-05-10 15:02:40 <cely> algitbot: retry master
2024-05-10 15:02:51 <cely> algitbot: retry master
2024-05-10 15:03:44 <cely> algitbot: retry master
2024-05-10 15:05:39 <cely> algitbot: retry master
2024-05-10 15:06:36 <cely> algitbot: retry master
2024-05-10 15:11:37 <cely> algitbot: retry master
2024-05-10 15:13:10 <cely> build-3-20-x86_64 has 179 aports left to build
2024-05-10 15:39:46 <cely> algitbot: retry master
2024-05-10 16:00:57 <cely> algitbot: retry master
2024-05-10 16:03:05 <cely> build-3-20-x86_64 has landed on ghc again
2024-05-10 16:04:27 <cely> I probably won't be around to see if fail again (well.....i hope it doesn't)
2024-05-10 16:04:31 <cely> s/if/it/
2024-05-10 16:20:40 <cely> algitbot: retry master
2024-05-10 16:50:19 <ikke> nmeum: 6
2024-05-10 16:50:21 <ikke> ^
2024-05-10 17:41:06 <celie> algitbot: retry master
2024-05-10 20:09:53 <nmeum> ikke: the ghc failure looks like a python 3.12 issue or something, will try to have a look on the weekend
2024-05-11 00:46:55 <celie> algitbot: retry master
2024-05-11 00:49:41 <celie> algitbot: retry master
2024-05-11 01:15:23 <cely> algitbot: retry master
2024-05-11 01:43:06 <cely> algitbot: retry master
2024-05-11 01:44:35 <cely> perl-sys-cpu failed on riscv64
2024-05-11 01:45:04 <cely> That's one perl-* aport i didn't claim maintainership of, as i think it's been deleted from CPAN
2024-05-11 01:45:40 <cely> I think it's still a dependency of a few other aports though
2024-05-11 01:48:44 <cely> Looking at the tests file, it seems it is failing test 3 (cpu speed), and 4 (cpu type)
2024-05-11 01:49:18 <cely> Probably this is the first time tests are actually running on riscv64
2024-05-11 01:50:40 <cely> Seems like it is only required by community/zoneminder, which is disabled for riscv64 already
2024-05-11 01:50:48 <cely> So, maybe let's just disable perl-sys-cpu
2024-05-11 01:50:50 <cely> for riscv64
2024-05-11 01:54:11 <cely> Let me see if tests also fail in riscv64 CI
2024-05-11 01:55:30 <cely> Ok, it fails too
2024-05-11 01:58:07 <cely> Hmm, Debian fixed this by marking the 2 tests as "TODO"
2024-05-11 02:00:13 <cely> I just realized that the APKBUILD also disables tests for aarch64
2024-05-11 02:05:35 <cely> and yes, the test also fails on aarch64
2024-05-11 02:07:27 <cely> lol, from the perl-sys-cpu test file: "We start with some black magic to print on failure."
2024-05-11 03:57:26 <cely> algitbot: retry master
2024-05-11 04:04:57 <cely> riscv64 has reached <1000 aports left
2024-05-11 04:07:18 <cely> algitbot: retry master
2024-05-11 04:25:31 <cely> algitbot: retry master
2024-05-11 04:33:07 <cely> riscv64 has 977, and x86_64 has 176 left
2024-05-11 04:48:37 <cely> algitbot: retry master
2024-05-11 04:49:04 <cely> algitbot: retry master
2024-05-11 04:49:35 <cely> algitbot: retry master
2024-05-11 04:51:18 <cely> I wonder if we can get to <100 for x86_64 by the end of today
2024-05-11 05:29:16 <cely> algitbot: retry master
2024-05-11 07:28:31 <cely> 159 aports left for x86_64
2024-05-11 07:38:20 <cely> With virt-manager failing tests disabled, now rnp should be the last blocker on armhf :)
2024-05-11 07:38:58 <cely> algitbot: retry master
2024-05-11 07:39:36 <cely> and maybe ppc64le too
2024-05-11 07:40:23 <cely> algitbot: retry master
2024-05-11 07:40:39 <cely> algitbot: retry master
2024-05-11 07:41:28 <cely> algitbot: retry master
2024-05-11 07:43:25 <cely> algitbot: retry master
2024-05-11 07:47:41 <cely> algitbot: retry master
2024-05-11 07:55:00 <cely> algitbot: retry master
2024-05-11 08:52:50 <nmeum> fix for rkward in !65773
2024-05-11 08:55:24 <ikke> 👍
2024-05-11 09:01:59 <nmeum> ncopa: haha, looks like we look at the same thing
2024-05-11 09:02:09 <nmeum> *looked
2024-05-11 09:02:27 <ncopa> nmeum: indeed. i in parallel was looking at ghc :)
2024-05-11 09:02:41 <nmeum> ncopa: your patch is missing the .data() invocation on the QByteArray though. this should fail check or at least it did for my patch
2024-05-11 09:03:11 <ncopa> oh  ok. feel free to fix it
2024-05-11 09:03:20 <ncopa> im off for today now
2024-05-11 09:03:41 <nmeum> sure, have a nice day :)
2024-05-11 09:03:52 <ncopa> there is also the rnp, which should be reported upstream
2024-05-11 09:04:03 <ncopa> you too! thanks!
2024-05-11 09:04:17 <nmeum> rnp is fixed by !65414
2024-05-11 09:04:42 <ncopa> awesome!
2024-05-11 09:23:03 <ikke> bootstrapping openjdk21
2024-05-11 13:19:14 <cely> algitbot: retry master
2024-05-11 13:40:07 <cely> algitbot: retry master
2024-05-11 13:51:32 <cely> I hope build-3-20-riscv64 and build-3-20-x86_64 are not both stuck
2024-05-11 13:53:30 <ikke> x86_64 seems to be still going
2024-05-11 13:54:26 <ikke> rv64 may be hanging
2024-05-11 14:02:28 <ikke> algitbot: retry master
2024-05-11 15:37:24 <celie> algitbot: retry master
2024-05-11 16:45:50 <celie> algitbot: retry master
2024-05-11 17:06:27 <celie> algitbot: retry master
2024-05-12 01:56:35 <celie> algitbot: retry master
2024-05-12 02:31:25 <celie> Oh now, build-3-20-x86_64 started building Deno again
2024-05-12 03:16:29 <cely> algitbot: retry master
2024-05-12 03:16:51 <cely> 901 aports left for riscv64
2024-05-12 03:16:55 <cely> community
2024-05-12 04:43:19 <cely> algitbot: retry master
2024-05-12 04:46:44 <cely> algitbot: retry master
2024-05-12 05:15:09 <cely> algitbot: retry master
2024-05-12 06:04:12 <cely> riscv64 is building py3-django-webpack-loader again
2024-05-12 06:08:16 <ikke> I already told it not to do that, that naughty builder
2024-05-12 06:09:04 <cely> When that was built on edge, it took 2.5 hours
2024-05-12 06:09:37 <ikke> There is progress, last time there was one '.' as the last output, now it's '..'
2024-05-12 06:11:06 <ikke> I'll let it continue
2024-05-12 06:12:02 <cely> What about the WebkitGTKs on ARM builders?
2024-05-12 06:13:21 <cely> Having 2 copies of it being built on all 3 archs can't be a good thing..
2024-05-12 06:13:25 <ikke> nope
2024-05-12 06:14:24 <ikke> Host is desperately looking for scrapes of free memory
2024-05-12 06:14:55 <cely> Do all 3 archs share the same host?
2024-05-12 06:15:14 <ikke> yes
2024-05-12 06:15:20 <cely> Wow
2024-05-12 06:15:26 <cely> That would be 6 copies of WebkitGTK
2024-05-12 06:16:31 <ikke> I'm rebooting the host
2024-05-12 06:16:34 <ikke> If I can
2024-05-12 12:34:58 <nmeum> cely: is there any specific reason why you use a custom basename macro for frr instead of including libgen.h for musl's version?
2024-05-12 12:35:50 <cely> I think it's due to const vs non-const
2024-05-12 12:35:58 <cely> The libgen.h version is non-const
2024-05-12 12:36:36 <nmeum> yes, it modifies the input buffer but POSIX does not require it to remain unmodified
2024-05-12 12:37:02 <nmeum> does frr require it to remain unmodified?
2024-05-12 12:37:45 <cely> I think i was made aware of this after seeing the discussion in !62810
2024-05-12 12:40:16 <nmeum> I see
2024-05-12 12:40:44 <cely> and if you look through the log file for -r1 that you have in #16106
2024-05-12 12:40:57 <cely> for frr-10.0-r1
2024-05-12 12:41:01 <cely> and search for libgen.h
2024-05-12 12:41:17 <cely> You see a "warning: type basename does not match original declaration"
2024-05-12 12:41:42 <cely> Not sure why it included libgen.h automatically
2024-05-12 12:41:58 <cely> When earlier it gave it an implicit declaration instead
2024-05-12 12:43:14 <cely> Anyway, so when i've worked on patching basename, i check for const, and if i see it i patch it with the macro instead of including libgen.h
2024-05-12 12:44:04 <nmeum> well the mismatch thing is an lto error, so that probably happpens when optimzing across multiple translation units as some include libgen.h
2024-05-12 12:44:13 <cely> Ok
2024-05-12 12:44:43 <nmeum> while the implicit declaration is a warning emitted for the zebra_netns_notify.c translation unit which doesn't include libgen.h
2024-05-12 12:45:12 <nmeum> checking if the input string is expected to be const makes sense indeed
2024-05-12 12:45:16 <nmeum> thanks for clarifying! :)
2024-05-12 12:45:51 <cely> You're welcome
2024-05-12 14:04:15 <cely> Hmm, so J0WI has merged rnp 0.17.1, but sadly the ARM builders are......still fighting to build WebkitGTK
2024-05-12 14:05:17 <cely> and x86 still has cargo-edit tests which are segfaulting, so the only arch that was unblocked for 3.20 is ppc64le
2024-05-12 14:06:20 <cely> algitbot: retry master
2024-05-12 14:08:32 <cely> algitbot: retry 3.19-stable
2024-05-12 14:08:56 <ikke> And I don't have OOB access to the builder atm, so I cannot force reboot it
2024-05-12 14:09:02 <ikke> ssh is hanging
2024-05-12 14:09:18 <cely> WebkitGTK killed the builder :(
2024-05-12 14:10:45 <ikke> CPU System time is 100%
2024-05-12 14:10:49 <ikke> or close to
2024-05-12 14:10:59 <cely> How is Deno doing on build-3-20-x86_64?
2024-05-12 14:11:33 <ikke> Not a lot is happening
2024-05-12 14:11:48 <ikke> thread 'main' panicked at cli/lsp/tsc.rs:1171:65:
2024-05-12 14:11:56 <ikke> called `Result::unwrap()` on an `Err` value: TypeError: serde_v8 error: invalid type; expected: object, got: string
2024-05-12 14:12:32 <ikke> So a panic that causes it to hang
2024-05-12 14:13:05 <ikke> algitbot: retry master
2024-05-12 14:17:53 <cely> Hm, that's ^ the Go rebuild, not 3.20
2024-05-12 14:18:05 <cely> *continues waiting*
2024-05-12 14:24:01 <ikke> *The waiting intensifies*
2024-05-12 14:24:34 <ikke> Our monitoring sporadically gets some data from the host
2024-05-12 14:24:47 <cely> for ARM?
2024-05-12 14:24:49 <ikke> Yes
2024-05-12 14:25:02 <ikke> Last what I see is ~30m ago
2024-05-12 14:25:57 <cely> There goes cargo-edit
2024-05-12 14:26:27 <cely> 108 aports left for x86_64 3.20 community
2024-05-12 14:26:39 <cely> ...
2024-05-12 14:26:51 <cely> 109 now with the addition of py3-channels
2024-05-12 14:28:33 <cely> Oh no! Deno again :(
2024-05-12 14:29:49 <ikke> 
ACTION wonders if would should use something like earlyoom on the host

2024-05-12 14:29:54 <ikke> if we*
2024-05-12 14:31:58 <cely> Speaking of earlyoom, i took a look at the latest upgrade (1.8.2), saw that it only modified the systemd service file, and decided to ignore it
2024-05-12 14:37:18 <cely> Phew, py3-stestr has finished building on riscv64
2024-05-12 14:39:49 <ikke> Yeah, I see some projects even bumping versions for CI changes 
2024-05-12 14:39:56 <ikke> like, why
2024-05-12 14:43:41 <cely> rqlite just did that, released 5 versions in a day
2024-05-12 14:53:56 <cely> Ah, there we go
2024-05-12 14:55:02 <cely> I wonder if anyone expected s390x and ppc64le to be the first 2 archs to finish building 3.20
2024-05-12 14:57:12 <ikke> Usually they have less to build
2024-05-12 14:57:24 <ikke> Packages get easier disabled for those arches
2024-05-12 17:27:20 <ikke> ooohg
2024-05-12 17:27:36 <ikke> access again
2024-05-12 18:05:51 <ikke> FYI, I've stopped the arm edge builders to prevent it from exhausting all memory again
2024-05-12 18:06:16 <ikke> algitbot: retry master
2024-05-12 19:23:15 <ikke> algitbot: retry master
2024-05-12 19:23:52 <ikke> algitbot: retry master
2024-05-12 19:32:14 <ikke> algitbot: retry master
2024-05-12 20:12:49 <PureTryOut> algitbot: retry master
2024-05-12 20:40:32 <ikke> algitbot: retry master
2024-05-12 21:05:53 <ikke> algitbot: retry master
2024-05-13 02:19:49 <celie> algitbot: retry master
2024-05-13 02:20:56 <celie> algitbot: retry master
2024-05-13 03:07:11 <cely> I don't think we can leave the builders in a failed state for so long
2024-05-13 03:07:18 <cely> So:
2024-05-13 03:10:28 <cely> algitbot: retry master
2024-05-13 03:31:46 <cely> Ok, why did s390x get stuck on gitlab-runner :/
2024-05-13 03:34:18 <cely> Oh, phew...s390x on edge completed
2024-05-13 03:34:26 <cely> Hopefully, 3.20 will follow
2024-05-13 03:35:04 <cely> algitbot: retry master
2024-05-13 04:17:54 <cely> I think something is going on with the s390x CI runner
2024-05-13 04:25:20 <cely> algitbot: retry 3.19-stable
2024-05-13 04:27:59 <cely> Ok, so 5 archs (s390x, ppc64le, x86, armhf, and armv7) have uploaded 3.20 community now
2024-05-13 04:28:33 <cely> aarch64 still has a few blockers
2024-05-13 04:29:02 <cely> algitbot: retry master
2024-05-13 04:29:57 <cely> jellyfin, jellyfin-web, neo4j..still trying to see what the 4th aport for aarch64 is
2024-05-13 04:30:00 <cely> algitbot: retry master
2024-05-13 04:31:23 <cely> algitbot: retry master
2024-05-13 04:32:11 <cely> Ah, it's gitlab-runner, and that hopefully shouldn't fail
2024-05-13 04:32:16 <cely> It didn't
2024-05-13 04:32:46 <cely> So, 3 blockers left for aarch64: jellyfin, jellyfin-web, and neo4j
2024-05-13 04:33:09 <cely> and i'll re-enable jellyfin for armv7 after that has uploaded community
2024-05-13 04:37:06 <cely> and the Go rebuild for s390x has completed, with Dendrite finally passing
2024-05-13 04:48:02 <cely> algitbot: retry master
2024-05-13 04:49:06 <cely> algitbot: retry master
2024-05-13 04:49:33 <cely> algitbot: retry master
2024-05-13 04:56:45 <cely> algitbot: retry master
2024-05-13 05:00:46 <cely> 90 aports left for x86_64 community
2024-05-13 05:16:08 <cely> 78 aports left for x86_64 community
2024-05-13 05:17:20 <cely> ^ and the Go rebuild in 3.19 has completed
2024-05-13 05:40:44 <cely> algitbot: retry master
2024-05-13 05:44:29 <cely> algitbot: retry master
2024-05-13 05:52:20 <cely> So, neo4j passed on x86_64..but not on aarch64
2024-05-13 05:57:21 <cely> 65 aports left for x86_64 community
2024-05-13 06:01:17 <cely> Passed on edge, failed on 3.20
2024-05-13 06:01:24 <cely> algitbot: retry master
2024-05-13 06:24:30 <cely> 52 aports left for x86_64 community
2024-05-13 07:00:33 <cely> algitbot: retry master
2024-05-13 07:07:33 <cely> riscv64 finished gotosocial before s390x
2024-05-13 07:08:14 <cely> algitbot: retry master
2024-05-13 07:09:23 <cely> algitbot: retry master
2024-05-13 07:09:39 <cely> algitbot: retry master
2024-05-13 07:21:31 <cely> 42 aports left for x86_64 community
2024-05-13 07:30:15 <cely> Finally <40 aports for x86_64 :)
2024-05-13 07:38:57 <cely> 30 aports left for x86_64 community
2024-05-13 07:42:13 <cely> ^ s390x has finally completed gotosocial on edge
2024-05-13 08:00:37 <cely> Maybe it's time to bring build-edge-armhf back online?
2024-05-13 08:02:30 <cely> 20 aports left for x86_64 community (not including the new KF 6.2.0 aports that were just merged)
2024-05-13 08:34:10 <cely> s390x is moving very slowly
2024-05-13 08:34:31 <cely> algitbot: retry master
2024-05-13 08:39:11 <cely> algitbot: retry master
2024-05-13 13:01:50 <cely> algitbot: retry master
2024-05-13 13:02:20 <cely> algitbot: retry master
2024-05-13 14:26:30 <cely> Oops, it seems riscv64 was retried before i pushed my fix?
2024-05-13 14:27:41 <cely> It will get it the next time then, unless the builder suddenly got a speed boost and can finish compiling Rust tests in 10 minutes
2024-05-13 17:19:59 <cely> algitbot: retry master
2024-05-13 17:34:00 <cely> I have a feeling that aarch64 will also fail to build Deno if !check is removed for it
2024-05-13 17:35:07 <omni> new aport*
2024-05-13 17:50:20 <celie> algitbot: retry master
2024-05-13 17:54:59 <ikke> ^ sus
2024-05-13 18:02:08 <celie> algitbot: retry master
2024-05-13 18:03:59 <celie> algitbot: retry master
2024-05-13 19:21:44 <ncopa> algitbot: retry master
2024-05-13 22:00:42 <ptrc> fwiw, the last two commits don't actually rebuild anything
2024-05-14 01:24:56 <celie> algitbot: retry master
2024-05-14 03:24:44 <cely> algitbot: retry master
2024-05-14 03:25:43 <cely> algitbot: retry master
2024-05-14 03:27:27 <cely> algitbot: retry master
2024-05-14 03:29:53 <cely> algitbot: retry master
2024-05-14 03:34:12 <cely> Kakoune probably needs `make -j1 install` in package(), but so far, retrying has managed to make it pass on s390x and ppc64le
2024-05-14 03:34:14 <cely> algitbot: retry master
2024-05-14 03:44:36 <cely> Seems to have worked
2024-05-14 03:44:55 <cely> Let's see what build-edge-riscv64 says
2024-05-14 05:47:41 <cely> algitbot: retry master
2024-05-14 05:51:35 <cely> algitbot: retry master
2024-05-14 08:11:39 <cely> algitbot: retry master
2024-05-14 08:35:05 <cely> algitbot: retry master
2024-05-14 08:41:57 <cely> Ah, there's build-3-20-aarch64 having finished uploading community :)
2024-05-14 09:00:24 <cely> algitbot: retry master
2024-05-14 12:45:49 <cely> algitbot: retry master
2024-05-14 13:16:59 <cely> algitbot: retry master
2024-05-14 14:07:26 <cely> algitbot: retry master
2024-05-14 14:32:19 <cely> There goes Deno
2024-05-14 14:38:00 <cely> 
ACTION ponders what it would take to fix a 3rd Java aport (after java-lz4 and neo4j)

2024-05-14 15:19:56 <cely> build-3-20-x86_64 is back to building Deno
2024-05-14 15:20:49 <ikke> cely: still expected to hang?
2024-05-14 15:21:32 <cely> I think so, i don't think we've changed anything
2024-05-14 15:21:35 <ikke> ok
2024-05-14 15:22:01 <cely> I'm running 1.42.4 through CI, but i'm expecting some tests to fail
2024-05-14 15:31:22 <ncopa> algitbot: retry master
2024-05-14 15:48:40 <cely> I see a lot of failures in Deno 1.42.4 tests :(
2024-05-14 15:56:28 <cely> I see a lot more failure in 1.42.4 than 1.43.3
2024-05-14 16:11:15 <ikke> cely: so that's progress, i guess?
2024-05-14 16:11:18 <ikke> oh, no
2024-05-14 16:11:19 <ikke> backwards
2024-05-14 16:12:52 <cely> What's backwards?
2024-05-14 16:13:15 <ikke> I mean, .4 has more failures than .3, so not progress, its getting worse
2024-05-14 16:13:46 <cely> Major version, major version
2024-05-14 16:14:42 <omni> potato tomato
2024-05-14 16:15:19 <omni> I've recently typed digits in the wrong order quit eoften
2024-05-14 16:15:54 <cely> It's 1.42.4 vs 1.43.3
2024-05-14 16:16:23 <cely> I'm looking through old npm versions to find out which one causes the lone 1.43.3 failing test to fail
2024-05-14 16:17:34 <ikke> Ah, reading is an art
2024-05-14 16:17:45 <omni> as is typing!
2024-05-14 16:20:39 <cely> Wish me luck
2024-05-14 16:21:30 <cely> Bingo
2024-05-14 16:21:47 <cely> The version is in between 10.5.0 to 10.7.0
2024-05-14 16:21:54 <cely> So, a new change, no wonder Deno upstream doesn't account for it
2024-05-14 16:21:56 <omni> 🍀
2024-05-14 16:24:02 <cely> Narrowed it down to between npm 10.5.1 and 10.6.0
2024-05-14 16:24:29 <cely> Now to see if i can find the exact commit
2024-05-14 16:25:00 <ikke> 
ACTION shakes head how test failures are related to the version of the package manager

2024-05-14 16:29:59 <cely> https://github.com/npm/cli/pull/7414
2024-05-14 16:32:01 <omni> what now then...
2024-05-14 16:32:06 <omni> algitbot: retry master
2024-05-14 16:34:32 <cely> So, it's just a s/ERR!/error/
2024-05-14 16:48:12 <omni> algitbot: retry master
2024-05-14 17:04:44 <cely> Hmm, i didn't notice the previous Deno MR
2024-05-14 18:01:27 <cely> algitbot: retry master
2024-05-14 19:14:06 <omni> until now!
2024-05-14 19:29:01 <andypost[s]> omni: looks like deno is build 3rd day
2024-05-14 20:23:44 <ikke> algitbot: retry master
2024-05-14 21:29:44 <omni> algitbot: retry master
2024-05-14 21:54:13 <ptrc> ( working on polishing loongarch64 stuff, none of these commits actually rebuild anything if anyone was worried :) )
2024-05-14 23:12:56 <omni> algitbot: retry master
2024-05-14 23:14:05 <omni> algitbot: retry master
2024-05-15 00:36:23 <celie> algitbot: retry master
2024-05-15 00:57:16 <celie> So, Deno's npx non-existent test passed after i patched it but some other test failed instead: "specs::cert::cafile_install"
2024-05-15 00:58:49 <celie> "/tmp/deno-cli-testRs6M7M/./bin/echo_test: exec: line 3: deno: not found"
2024-05-15 00:59:01 <celie> algitbot: retry master
2024-05-15 01:03:41 <celie> algitbot: retry master
2024-05-15 01:41:57 <celie> algitbot: retry master
2024-05-15 01:53:16 <celie> algitbot: retry master
2024-05-15 01:54:23 <celie> algitbot: retry master
2024-05-15 01:56:57 <celie> algitbot: retry master
2024-05-15 01:59:05 <celie> algitbot: retry master
2024-05-15 02:14:24 <cely> algitbot: hi
2024-05-15 02:14:27 <cely> algitbot: retry master
2024-05-15 02:14:54 <cely> Wow, a lag time of 2 minutes
2024-05-15 04:53:51 <cely> algitbot: hi
2024-05-15 05:49:50 <cely> :)
2024-05-15 05:49:53 <cely> Finally uploaded
2024-05-15 05:50:21 <cely> Whrn riscv64 is done, it will be finally finally finally uploaded
2024-05-15 05:50:25 <cely> When*
2024-05-15 06:12:38 <omni> uhm... why didn't the aarch64 and armv7 builders start?
2024-05-15 07:31:06 <cely> algitbot: retry master
2024-05-15 12:13:09 <cely> Interesting, so apparently specs::cert::cafile_install runs "$builddir/target/release/deno install --cert RootCA.pem -n echo_test --root /tmp/<something> https://localhost:5454/echo.ts"
2024-05-15 12:14:58 <cely> Perhaps "$builddir/target/release" should be placed in $PATH so the test can find `deno`
2024-05-15 13:01:36 <cely> algitbot: retry master
2024-05-15 13:12:36 <fabricionaweb> ah come on it were passing on the mr 😞
2024-05-15 14:10:16 <cely> algitbot: retry master
2024-05-15 14:12:54 <cely> algitbot: retry master
2024-05-15 14:38:01 <cely> algitbot: retry master
2024-05-15 14:38:09 <fabricionaweb> should I disable traefik tests for s390x?
2024-05-15 14:39:32 <cely> That would be a question better answered by Traefik's maintainer
2024-05-15 14:39:46 <cely> Maybe you could try skipping only the test(s) that fail
2024-05-15 14:40:12 <fabricionaweb> let me try
2024-05-15 15:38:54 <fabricionaweb> no bueno, now its failing on another test
2024-05-15 15:53:40 <fabricionaweb> I retried 3 times and it worked now
2024-05-15 16:06:50 <cely> algitbot: retry master
2024-05-15 16:14:21 <cely> Hmm, so i guess netpbm finally passed tests
2024-05-15 16:38:44 <cely> algitbot: retry master
2024-05-15 17:02:20 <fabricionaweb> i sent the MR to skip the one that fails on ratelimiter but the one that happens on server seems important... but its very intermintent, sometimes pass sometimes not LOL
2024-05-15 20:42:26 <ncopa> algitbot: retry master
2024-05-16 00:40:12 <ptrc> algitbot: retry master
2024-05-16 03:49:03 <cely> algitbot: hi
2024-05-16 03:50:04 <cely> 25 more aports left for riscv64 community
2024-05-16 03:57:37 <zcrayfish> nice
2024-05-16 03:59:05 <cely> 12 now
2024-05-16 04:03:57 <cely> 7 more!
2024-05-16 04:09:16 <cely> I think i'll just temp disable ffcall if it's the last blocker for riscv64
2024-05-16 04:10:18 <cely> ffcall is only used by clisp, which is x86_64-only anyway
2024-05-16 04:12:58 <cely> Well, maybe it won't be me doing that, as the builder is now working on scryer-prolog, which took over an hour the last time it built and that was without running tests (though i don't know if that was still using emulated riscv64)
2024-05-16 04:55:01 <cely> I wonder if we'll get 3.20-rc1 or reach 66000 MRs on gitlab.a.o first
2024-05-16 05:09:17 <ikke> algitbot: retry master
2024-05-16 06:06:43 <cely> build-3-20-riscv64 is finally finally finally uploading community \o/
2024-05-16 06:22:16 <zcrayfish> nice.
2024-05-16 06:35:45 <iggy> that is quite a feat, great job
2024-05-16 09:03:58 <omni> algitbot: retry master
2024-05-16 11:19:58 <omni> ncopa: uhm, surely not 3.10
2024-05-16 11:31:48 <cely> Oops
2024-05-16 11:31:59 <ikke> mkinitfs?
2024-05-16 11:32:10 <ikke> -VERSION:= 3.9.1
2024-05-16 11:32:13 <ikke> +VERSION:= 3.10.0_rc1
2024-05-16 11:32:20 <cely> Ah, so it's not aports
2024-05-16 11:32:41 <ikke> nope
2024-05-16 11:33:06 <ikke> builders are not idle anyway
2024-05-16 11:33:12 <cely> I was also wondering how aports could be tagged when the builders aren't idle
2024-05-16 11:33:14 <cely> Right
2024-05-16 12:04:33 <cely> Poor arti can't compete for resources with the 3 Chromiums+1 Deno
2024-05-16 12:05:21 <fabricionaweb> ah that maybe was the reason for traefik failures yesterday
2024-05-16 12:08:51 <ikke> Tasks: 893, 263 thr, 623 kthr; 80 running
2024-05-16 12:12:37 <cely> I hope it is not looking as bad as the time when it tried building 6 WebkitGTKs
2024-05-16 12:17:03 <ikke> then I could not even access the host
2024-05-16 12:17:19 <ikke> memory usage is low atm
2024-05-16 12:17:45 <ikke> 215G memory available
2024-05-16 12:18:19 <ikke> last 12h minimum was 160G mem available
2024-05-16 12:19:15 <ikke> Now 95% CPU User time instead of kernel
2024-05-16 12:19:37 <ikke> algitbot: retry 3.19-stable
2024-05-16 12:20:05 <ikke> The CPU is put to good use
2024-05-16 12:40:22 <cely> algitbot: retry master
2024-05-16 13:07:14 <cely> Thunderbird getting uploaded
2024-05-16 14:50:05 <cely> Now 4 copies of Chromium are being built by ARM
2024-05-16 16:30:02 <omni> ncopa: sorry, didn't see that it was mkinitfs 
2024-05-16 16:35:21 <cely> Next target: will we get to 66050 MRs in Gitlab before 3.20-rc1 is released :)
2024-05-16 16:35:45 <cely> algitbot: retry master
2024-05-16 16:38:29 <ikke> We already surpassed 65536
2024-05-16 16:38:52 <cely> Haha
2024-05-16 16:39:56 <cely> I wonder what that MR was about
2024-05-16 16:39:59 <cely> !65536
2024-05-16 16:40:08 <cely> lol
2024-05-16 16:40:17 <fabricionaweb> I want send neovim 0.10 but Im looking to test and tests are failing 😅
2024-05-16 16:42:18 <ikke> sad, just a closed MR
2024-05-16 16:43:35 <cely> Oh, now i looked closer
2024-05-16 16:44:00 <cely> It was probably an automatic MR creation fail
2024-05-16 16:44:33 <cely> I thought it was my MR (from the title)
2024-05-16 17:05:57 <celie> algitbot: retry master
2024-05-16 17:18:05 <fabricionaweb> just fails
2024-05-16 17:18:56 <ikke> just fix it
2024-05-16 17:20:29 <fabricionaweb> my gitea also just fails on riscv64 timeout from npm
2024-05-16 17:57:44 <fabricionaweb> just passed
2024-05-16 19:46:24 <ncopa> omni: no worries!
2024-05-17 00:37:41 <celie> Next target: will we reach !66100 MRs before 3.20-rc1 :)
2024-05-17 01:35:03 <cely> algitbot: retry master
2024-05-17 07:12:53 <cely> lol
2024-05-17 07:13:05 <cely> Everytime i see "rc1" my heart skips a beat
2024-05-17 07:13:19 <cely> Then i look closer and it isn't aports
2024-05-17 07:13:32 <fossdd> haha
2024-05-17 10:35:53 <ikke> ^ sfdisk not found
2024-05-17 10:37:44 <ikke> algitbot: retry master
2024-05-17 10:39:40 <ikke> +/dev/dasda is not a block device
2024-05-17 10:39:42 <ikke> +/dev/dasdb is not a block device
2024-05-17 10:39:52 <ikke> for s390x
2024-05-17 12:03:47 <ncopa> algitbot: retry master
2024-05-17 15:17:34 <nmeum> algitbot: retry master
2024-05-17 15:48:23 <cely> algitbot: retry master
2024-05-17 16:56:21 <cely> algitbot: retry master
2024-05-17 18:27:23 <celie> algitbot: retry master
2024-05-17 18:44:38 <celie> algitbot: retry master
2024-05-17 18:45:46 <celie> algitbot: retry master
2024-05-18 00:30:21 <celie> algitbot: retry master
2024-05-18 01:39:38 <celie> algitbot: retry master
2024-05-18 03:12:09 <celie> algitbot: retry master
2024-05-18 03:22:33 <cely> algitbot: retry master
2024-05-18 03:23:04 <cely> algitbot: retry master
2024-05-18 03:26:31 <cely> algitbot: retry master
2024-05-18 03:27:46 <cely> algitbot: retry master
2024-05-18 03:31:11 <cely> Why are manpages being converted to text :/
2024-05-18 03:44:03 <cely> algitbot: retry master
2024-05-18 03:55:27 <cely> algitbot: retry master
2024-05-18 04:53:38 <cely> algitbot: retry master
2024-05-18 04:59:07 <cely> algitbot: retry master
2024-05-18 05:01:30 <cely> algitbot: retry master
2024-05-18 05:15:40 <cely> algitbot: retry master
2024-05-18 05:53:35 <cely> algitbot: retry master
2024-05-18 06:29:50 <omni> maybe git-lfs2 isn't needed anymore?
2024-05-18 06:34:39 <cely> Maybe you'll have to ask on Gitlab
2024-05-18 06:41:16 <omni> !66120
2024-05-18 07:25:23 <cely> algitbot: retry master
2024-05-18 09:36:18 <nmeum> algitbot: retry master
2024-05-18 09:43:52 <cely> algitbot: retry master
2024-05-18 09:59:58 <omni> I'm holding off merging !66120 to give jirutka a chance to have a say, but bratkartoffel, who originally reported the issue with git-lfs v3, doesn't need it anymore so it would probably be fine to merge if needed to get things moving
2024-05-18 11:33:19 <cely> algitbot: retry master
2024-05-18 13:17:42 <omni> algitbot: retry master
2024-05-18 14:17:10 <cely> algitbot: retry master
2024-05-18 14:28:23 <cely> algitbot: retry master
2024-05-18 14:40:06 <ikke> Seems like it fails due to upgraded git?
2024-05-18 14:40:21 <ikke> fatal: active `post-checkout` hook found during `git clone` For security reasons, this is disallowed by default
2024-05-18 14:43:20 <cely> Probably
2024-05-18 14:43:29 <cely> There's already an MR to remove git-lfs2
2024-05-18 14:45:05 <ikke> !66120
2024-05-18 16:52:33 <ikke> algitbot: retry master
2024-05-18 17:05:34 <cely> ^ note to self: check out what's wrong later on, but for now i don't want to block the 3.20 builders (other archs didn't encounter this problem with tests)
2024-05-18 17:10:58 <cely> algitbot: retry master
2024-05-18 17:12:06 <cely> algitbot: retry master
2024-05-18 17:17:50 <cely> algitbot: retry master
2024-05-18 17:19:06 <cely> algitbot: retry master
2024-05-18 17:20:27 <cely> I think apparmor needs a pkgrel bump (i was surprised that i retried master and the builders immediately went back to community)
2024-05-18 17:20:52 <ikke> yes, it would
2024-05-18 17:21:39 <cely> I'm working on it
2024-05-18 17:24:38 <cely> algitbot: retry master
2024-05-18 17:27:57 <cely> algitbot: retry master
2024-05-18 17:28:26 <cely> build-3-20-aarch64 is back to building py3-virtualenv
2024-05-18 17:28:33 <cely> Oh, and it passed this time
2024-05-18 17:29:33 <cely> algitbot: retry master
2024-05-18 17:42:56 <cely> algitbot: retry master
2024-05-18 17:55:07 <celie> algitbot: retry master
2024-05-18 18:00:29 <celie> algitbot: retry master
2024-05-18 18:10:27 <celie> algitbot: retry master
2024-05-18 18:54:12 <ikke> w00t
2024-05-18 20:53:27 <ikke> ^ checksum missing
2024-05-18 21:13:22 <ptrc> sigh
2024-05-18 21:13:55 <ptrc> right
2024-05-18 23:29:23 <omni> algitbot: retry master
2024-05-19 00:46:19 <celie> algitbot: retry master
2024-05-19 02:34:44 <cely> algitbot: retry master
2024-05-19 02:56:33 <cely> 9 more aports left for x86_64 testing
2024-05-19 02:56:54 <cely> (mostly from the Go rebuild)
2024-05-19 03:21:09 <cely> Finally uploaded :)
2024-05-19 11:31:59 <omni> OOM victim
2024-05-19 11:38:15 <ikke> Out of memory: Killed process 31993 (cc1plus) total-vm:3210140kB, anon-rss:2967356kB, file-rss:0kB, shmem-rss:0kB, UID:1000 pgtables:6224kB oom_score_adj:0
2024-05-19 11:39:16 <omni> algitbot: retry master
2024-05-19 11:39:23 <omni> now that build-edge-aarch64 is done with it
2024-05-19 11:58:44 <omni> *sigh*
2024-05-19 11:59:03 <omni> with build-edge-x86_64 is done with it...
2024-05-19 13:01:04 <cely> algitbot: retry master
2024-05-20 05:22:08 <cely> Oops, SQLite tests are now running on 16 archs at the same time
2024-05-20 05:22:10 <cely> 
ACTION keeps fingers crossed

2024-05-20 05:26:40 <cely> :O
2024-05-20 05:26:43 <cely> s390x is the fastest?
2024-05-20 05:27:38 <iggy> does the sqlite test suite run all tests on all arches? did it just skip a bunch of tests?
2024-05-20 05:27:57 <iggy> (I could look, but I'm lazy)
2024-05-20 05:28:56 <cely> Let me see, it does print a summary of the number of tests ran
2024-05-20 05:29:18 <cely> s390x: "0 errors out of 377329 tests"
2024-05-20 05:30:52 <cely> Same number on x86_64
2024-05-20 05:30:59 <cely> Oh wait
2024-05-20 05:31:05 <cely> It's 377339 for x86_64
2024-05-20 05:32:52 <cely> So, 10 tests less than most of the other archs
2024-05-20 05:35:48 <cely> (Tests are parallelized for riscv64, i wonder if that made it slower this time (as 2 copies of the test suite are running at the same time))
2024-05-20 05:36:52 <cely> I hope it is not stuck on build-edge-riscv64
2024-05-20 05:37:13 <cely> Oh, thankfully
2024-05-20 05:39:28 <cely> So, criteria for moving to community (running the test suite), check
2024-05-20 05:40:42 <cely> Whether the tools can be built as part of main/sqlite is probably something for after 3.20, as it would very likely involve changing source tarball and resolving a circular dep between it and tcl, so not something that can be rushed with 3.20 just around the corner
2024-05-20 05:44:03 <cely> Anyway, i'm happy that there is at least some tests that can be run upon SQLite upgrades now, as i've often upgraded SQLite wondering if the upgrade will break something
2024-05-20 08:34:25 <cely> Wow, 4 languages having commits one after another
2024-05-20 08:34:55 <cely> Anyone want to add a 5th to the list?
2024-05-20 08:56:32 <cely> Hopefully the builders are able to finish building NodeJS
2024-05-20 09:04:03 <cely> Oh no :(
2024-05-20 09:04:38 <cely> 2 NodeJS + 1 QtWebEngine proved too much..
2024-05-20 09:11:00 <omni> it can be retried later
2024-05-20 09:13:26 <cely> armv7 is the first this time around
2024-05-20 09:14:36 <cely> There's your retry
2024-05-20 11:56:39 <ncopa> algitbot: retry master
2024-05-20 14:22:35 <cely> algitbot: retry master
2024-05-20 15:09:21 <cely> Spent some time chasing down the commit that caused a test failure
2024-05-20 15:09:56 <cely> So, paradoxically, was really happy when the failure occurred :)
2024-05-20 15:43:09 <cely> algitbot: retry master
2024-05-20 16:03:23 <cely> algitbot: retry master
2024-05-20 16:13:34 <cely> cppcheck has finally passed
2024-05-20 16:13:43 <cely> deno has also been uploaded on 3.20 x86_64, now only edge remains
2024-05-20 19:05:58 <ikke> rip util-linux
2024-05-20 19:06:46 <ikke> algitbot: retry master
2024-05-20 19:20:04 <ikke> seems to be flaky
2024-05-20 19:20:05 <ikke> algitbot: retry master
2024-05-20 20:54:40 <ncopa> algitbot: retry 3.18-stable
2024-05-20 21:27:41 <omni> algitbot: retry 3.17-stable
2024-05-21 02:04:06 <cely> Ugh
2024-05-21 02:04:25 <cely> So, something changed in the 3 days since !66090 was opened
2024-05-21 02:08:29 <cely> util-linux gained a new dmesg subpackage, and i took over maintainership of sqlite
2024-05-21 02:09:22 <cely> I'm betting on the former
2024-05-21 02:14:35 <cely> No, that's not it
2024-05-21 02:15:29 <cely> So much for wanting to close a long standing MR that's been assigned to me for review (!54727)
2024-05-21 02:20:21 <cely> 
ACTION remembers back to the day before 3.19 when NodeJS errors started appearing

2024-05-21 02:20:33 <cely> Seems like this time around, i've hit the jackpot
2024-05-21 02:27:20 <cely> Bingo
2024-05-21 02:27:29 <cely> The Busybox CVE fix commit is causing this problem
2024-05-21 02:28:56 <cely> Downgrading to busybox=1.36.1-r26 allows the lttng-ust tests to pass
2024-05-21 03:00:01 <cely> Phew
2024-05-21 06:53:02 <cely> OOM killer strikes again?
2024-05-21 06:55:53 <omni> is it possible to try them one at a time?
2024-05-21 06:56:35 <cely> Probably not
2024-05-21 06:57:10 <cely> but allowing armv7 and armhf to complete first should be of some help
2024-05-21 06:58:11 <cely> (all 3 archs run on the same host machine, so edge+3.20 makes that 6 copies being built at once)
2024-05-21 07:01:39 <cely> 32-bit ARMs are done with Clang, so should be safe to retry aarch64 now
2024-05-21 07:01:42 <cely> algitbot: retry master
2024-05-21 07:18:39 <cely> Finally done with Clang 18 :)
2024-05-21 16:33:04 <cely> algitbot: retry master
2024-05-22 06:00:11 <omni> algitbot: retry 3.17-stable
2024-05-22 06:00:55 <omni> algitbot: retry 3.16-stable
2024-05-22 08:58:19 <fossdd> o
2024-05-22 09:47:59 <fossdd> \o/
2024-05-22 16:30:22 <cely> algitbot: retry master
2024-05-22 16:37:07 <ptrc> algitbot: retry master
2024-05-22 16:37:41 <cely> algitbot: retry master
2024-05-22 16:53:49 <andypost[m]> algitbot: retry 3.20-stable
2024-05-22 21:08:58 <zcrayfish> wew. Now that 3.20 is out, I'd like to see about tackling updating the LXQt packages... 
2024-05-22 21:10:35 <zcrayfish> Biggest hurdle right now is libdbusmenu-lxqt, which would be a new package... It's a qt6 fork of libdbusmenu-qt. I'm wondering about the possibility of sending it straight to community and bypassing testing. 
2024-05-22 21:11:26 <zcrayfish> https://git.alpinelinux.org/aports/tree/community/libdbusmenu-qt/APKBUILD
2024-05-22 21:11:28 <zcrayfish> https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/65828/diffs?commit_id=62866fac6edb4a1dbb7e07fd648baa31555db2ac
2024-05-22 21:13:51 <zcrayfish> it's a dependency for the 2.x/qt6 versions of LXQt stage IV packages (i.e. these: https://github.com/lxqt/lxqt/wiki/Building-from-source#iv---all-remaining-packages-in-any-order )
2024-05-22 21:20:30 <zcrayfish> crap I meant to post all that in -devel. .... #fail
2024-05-23 02:24:38 <cely> algitbot: retry master
2024-05-23 07:55:58 <PureTryOut> algitbot: retry master
2024-05-23 07:56:16 <PureTryOut> algitbot: retry 3.20-stable
2024-05-23 07:57:04 <ptrc> PureTryOut: it looks like they're hitting a broken mirror?
2024-05-23 07:57:08 <PureTryOut> Why... Does it fail to retrieve sources on x86 architectures only?
2024-05-23 07:57:18 <PureTryOut> Seems like it, but only on x86_64 and x86 🤔
2024-05-23 07:57:26 <ptrc> probably location-based
2024-05-23 07:57:36 <PureTryOut> Ah yeah that sounds right
2024-05-23 09:43:58 <cely> algitbot: retry 3.20-stable
2024-05-23 10:59:13 <ptrc> okay um
2024-05-23 10:59:58 <ptrc> nobody saw anything
2024-05-23 11:04:06 <ikke> 👀
2024-05-23 11:04:40 <ptrc> first try
2024-05-23 11:53:05 <ikke> algitbot: retry master
2024-05-23 13:42:09 <cely> algitbot: retry 3.20-stable
2024-05-23 14:13:42 <cely> algitbot: retry master
2024-05-23 16:22:22 <cely> Trusting the test suite :)
2024-05-23 19:08:42 <PureTryOut> algitbot: retry master
2024-05-23 19:40:56 <PureTryOut> algitbot: retry master
2024-05-23 20:33:57 <PureTryOut> algitbot:  retry master
2024-05-23 20:34:12 <PureTryOut>  * algitbot: retry master
2024-05-23 21:00:13 <PureTryOut> I think riscv64 is stuck, it's been working on community/xdg-desktop-portal-kde for way too long now...
2024-05-23 21:01:37 <PureTryOut> algitbot: retry master
2024-05-23 21:36:08 <ikke> PureTryOut: there are network issues
2024-05-23 21:40:00 <zcrayfish> I wonder if that contributed to my job#1396450 failing
2024-05-24 07:13:39 <cely> algitbot: retry master
2024-05-24 07:24:18 <cely> algitbot: retry master
2024-05-24 10:46:59 <ikke> algitbot: retry master
2024-05-24 12:39:22 <cely> algitbot: retry master
2024-05-24 12:41:13 <cely> algitbot: retry master
2024-05-24 12:48:06 <cely> algitbot: retry master
2024-05-24 12:58:55 <cely> algitbot: retry master
2024-05-24 13:12:45 <cely> algitbot: retry master
2024-05-24 13:14:10 <cely> algitbot: retry master
2024-05-24 15:17:00 <ikke> algitbot: retry master
2024-05-24 15:17:10 <ikke> algitbot: retry 3.20-stable
2024-05-24 16:36:14 <cely> algitbot: retry master
2024-05-24 16:36:59 <cely> algitbot: retry master
2024-05-24 16:37:17 <cely> Ugh
2024-05-24 16:37:23 <cely> Why won't it build something else..
2024-05-24 16:37:25 <cely> algitbot: retry master
2024-05-24 16:38:06 <cely> (i just saw !66491 being closed, so not sure if s390x works for those packages or not)
2024-05-24 16:38:33 <cely> algitbot: retry master
2024-05-24 16:39:34 <cely> So x86_64 finally finished building Chromium!
2024-05-24 16:39:37 <Thermi> cely, I made an MR to fix this: 66498
2024-05-24 16:39:39 <Thermi> *!66498
2024-05-24 16:39:54 <Thermi> the title is a bit misleading because it largely disables s390x
2024-05-24 16:40:05 <cely> Welcome back from the Chromium abyss, build-edge-x86_64
2024-05-24 16:40:21 <Thermi> cely, aaah I see, so now it finally can catch up
2024-05-24 16:58:48 <Thermi> I'd be very happy if it could start skipping this one for now and just build its dependencies
2024-05-24 16:59:42 <ikke> It should build dependencies first, if it does not, it means there is some issue, either a circular dependency, or a hidden dependency
2024-05-24 17:00:09 <Thermi> I think I got it wrong
2024-05-24 17:00:42 <cely> What dependencies are you talking about?
2024-05-24 17:00:43 <Thermi> we need to take it out for now
2024-05-24 17:00:48 <cely> The dependencies are built
2024-05-24 17:00:52 <cely> Just not uploaded
2024-05-24 17:01:28 <cely> Each repository, main community testing, has to be completely unblocked for whatever's been built in there to be uploaded
2024-05-24 17:01:33 <Thermi> the reason is that the fix for this issue is in here: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/66498/diffs?commit_id=93ea6707f04c3ee7e523fd33b73a3447f3209c9f#cd14eea7b21e9c0621c58a110a26238e0a9e6945_7_6
2024-05-24 17:01:37 <ikke> but that does not matter for the builder
2024-05-24 17:01:40 <ikke> the builder has all packages locally
2024-05-24 17:02:30 <Thermi> and for that package's pipeliens to succeed we need this MR first: !65923
2024-05-24 17:02:52 <cely> ^ fluix: i hope you don't mind that i just got that commit in (trying to beat the Gitlab shutdown)
2024-05-24 17:02:54 <Thermi> and that one's pipelines fail because py3-fastapi is not built for s390x yet
2024-05-24 17:05:17 <Thermi> we need to take grommunio-admin-api out, it seems to be stuck on trying to build it
2024-05-24 17:05:43 <Thermi> (at least I think so)
2024-05-24 17:05:53 <fluix> cely: totally fine, thanks for doing so much :D
2024-05-24 17:06:15 <ikke> Thermi: you don't need to necessary remove it to fix it, just push a commit that fixes it and the builder should pick that up the next time
2024-05-24 17:06:22 <Thermi> I see
2024-05-24 17:06:44 <ikke> As long as dependencies are marked correctly, the builder first builds the dependency before building the package itself
2024-05-24 17:07:28 <ikke> But CI pipelines like cely mentioned don't see the already built but not uploaded packages yet
2024-05-24 17:09:08 <cely> If you want to know if the pipeline will succeed or not, you can always bump pkgrel on those aports and add them to the MR, then remove them after you've verified that CI is green
2024-05-24 17:09:29 <ikke> indeed
2024-05-24 17:09:50 <ikke> Any change the the APKBUILD would trigger a rebuild btw
2024-05-24 17:09:54 <ikke> even a whitespace change
2024-05-24 17:10:06 <ikke> (in CI)
2024-05-24 17:10:23 <cely> But adding a trailing whitespace would make lint unhappy ;)
2024-05-24 17:10:41 <cely> Could be a reminder to remove that before merging though
2024-05-25 01:04:34 <cely> algitbot: retry master
2024-05-25 01:05:05 <cely> algitbot: retry master
2024-05-25 01:29:06 <cely> algitbot: retry master
2024-05-25 07:14:00 <ikke> ERROR: plasma-workspace-wallpapers-6.0.5-r0.apk: UNTRUSTED signature
2024-05-25 07:14:02 <ikke> >>> ERROR: kinfocenter: Failed to create index
2024-05-25 07:14:04 <ikke> huh
2024-05-25 07:14:30 <cely> Maybe r0 was used before?
2024-05-25 07:15:43 <ikke> this is when adding a package to the index
2024-05-25 07:15:58 <ikke> and the builders do not use dl-cdn
2024-05-25 07:16:05 <cely> Ok
2024-05-25 07:17:35 <ikke> Don't see anything strange here: https://build.alpinelinux.org/buildlogs/build-3-20-riscv64/community/plasma-workspace-wallpapers/plasma-workspace-wallpapers-6.0.4-r0.log
2024-05-25 07:18:13 <cely> It's complaining about 6.0.5 though
2024-05-25 07:18:18 <ikke> Yes, just noticed
2024-05-25 07:19:09 <ikke> ok, a bunch of null bytes in the buildlog for 6.0.5, so I guess something crashed when that was built
2024-05-25 07:19:22 <ikke> I'll delete the package so that it gets built again
2024-05-25 07:19:58 <ikke> algitbot: retry 3.20-stable
2024-05-25 13:54:22 <cely> algitbot: retry master
2024-05-25 14:23:14 <cely> algitbot: retry master
2024-05-25 15:54:45 <cely> algitbot: retry master
2024-05-25 16:02:16 <cely> algitbot: retry master
2024-05-25 16:14:12 <cely> algitbot: retry master
2024-05-25 16:27:20 <cely> algitbot: retry master
2024-05-25 16:45:54 <cely> algitbot: retry master
2024-05-25 17:05:10 <cely> algitbot: retry master
2024-05-25 17:24:17 <cely> algitbot: retry master
2024-05-25 17:54:46 <cely> ...
2024-05-25 17:54:51 <fossdd> haha
2024-05-25 17:57:43 <cely> algitbot: retry master
2024-05-25 18:10:47 <cely> algitbot: retry master
2024-05-25 18:20:04 <celie> algitbot: retry master
2024-05-25 20:59:13 <ikke> Failed to start message bus: Error in file /etc/dbus-1/session.conf, line 1, column 0: no element found
2024-05-26 00:46:36 <celie> algitbot: retry master
2024-05-26 00:54:35 <celie> algitbot: retry master
2024-05-26 03:13:27 <cely> algitbot: retry master
2024-05-27 01:51:50 <celie> ...
2024-05-27 15:17:18 <cely> Hmm, i only saw messages for v3.20/main/aarch64 and armhf being uploaded...is my internet connection playing tricks on me again
2024-05-27 15:25:02 <ikke> cely: I see messages for all arches
2024-05-27 15:26:35 <cely> Now i see it
2024-05-27 15:26:56 <cely> Silly internet connection :(
2024-05-28 11:03:38 <ptrc> PureTryOut: ^
2024-05-28 11:03:58 <PureTryOut> but it succeeded on CI 😢
2024-05-28 11:04:36 <PureTryOut> algitbot: retry master
2024-05-28 11:06:19 <ptrc> yeah, it's quite odd tbh
2024-05-28 11:06:24 <ptrc> maybe just a one-off error
2024-05-28 11:06:41 <ikke> race condition?
2024-05-28 11:11:55 <ptrc> indeed a one-off issue 🙃
2024-05-30 09:17:34 <cely> algitbot: retry master
2024-05-30 17:30:44 <ptrc> algitbot: retry master
2024-05-30 17:41:17 <ptrc> algitbot: retry master
2024-05-30 19:36:18 <ptrc> algitbot: retry master
2024-05-31 10:50:19 <cely> ^ is also a rename of the aport
2024-05-31 10:52:30 <ikke> right, though, only in testing
2024-05-31 10:52:35 <cely> Hmm, but the reason ("required a rename of the pkg directory") makes me think setting `builddir` could have been used instead