On Thu, Aug 21, 2025 at 1:49 PM Frank Ch. Eigler <f...@redhat.com> wrote: > > Hi - > > > > > > koschei build Jul 06 - 55 minutes: > > > > > https://koji.fedoraproject.org/koji/taskinfo?taskID=134622296 > > > > > full build Jul 10 - 32 hours 13 min > > > > > https://koji.fedoraproject.org/koji/taskinfo?taskID=134741067 > > > > > > find-debuginfo: starting > > > > > Extracting debug info from 43 files > > > > > and has been there for hours. > > > > > > So, did the static debuginfo collection change affect this? [...] > > Yes, likely. A good question is *why*. These operations basically > copy potentially large files out and into .a files and perform very > little computation. Are the builders seriously RAM or I/O starved? >
I can reproduce this behavior on my local workstation and it's probably not RAM or I/O starved (64 GiB of RAM and a very fast SSD). The behavior with 5.2 is much, much slower than 5.1. I was able to build gdal 3.10 in a little under an hour with `fedpkg mockbuild` on the F42 buildroot. It was spending hours on single-threaded `ar` calls. Is there any possibility of parallelizing that? I gave up after about three hours on the 3.11 build on the F43 buildroot since I found this probable cause. > I'll do a trial build here with a relatively unconstrained machine for a > closer look. In the mean time, any package experiencing unacceptable > growth in build time or space can add this into their .spec to restore > the status quo ante: > > %undefine _preserve_static_debuginfo > > - FChE > -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
