[09:40] <cjwatson> (fixed last night while I was asleep)
[10:37] <cpaelzer> hi - in regard to build is there anything on my end that is better than cancel+restart if a build is locked up in "pkgstripfiles: waiting for lock" ?
[10:37] <cpaelzer> This one is an example https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4640/+build/21964944
[10:37] <cpaelzer> we all have learned to expect riscv64 to build slow, so I didn't realize it before
[10:37] <cpaelzer> and while I've seen other builds (on any arch) to loop through that a bit this one seems to hang on it for hours
[10:43] <cjwatson> cpaelzer: there is not
[10:43] <cjwatson> cpaelzer: you could try debugging it though :-)
[10:44] <cjwatson> cpaelzer: it's probably in pkgbinarymangler or pkg-create-dbgsym somewhere, I forget which
[10:44] <cpaelzer> I have when I've seen it long ago and it was as racy and heisen-buggy as you would expect :-)
[10:44] <cpaelzer> mangler rings a bell
[10:45] <cpaelzer> I'll cancel and restart for now, maybe after f-freeze there is time revisit the problem if it becomes more common
[10:45] <cpaelzer> in my experience it scales with the number of binary packages in a build
[10:46] <cpaelzer> IIRC dpdk was the one I saw it most of the time and that has >100 binary packages
[10:46] <cpaelzer> thanks cjwatson for the answer that there is no obvious way I miss, that at least makes me feel better when restarting it