[07:11] <LocutusOfBorg> https://launchpad.net/ubuntu/+source/ocaml-logs/0.7.0-2build8/+build/25561889
[07:11] <LocutusOfBorg> this  riscv64-qemu-lgw01-078  looks really stuck... I don't think it took 6h to install half dependencies
[08:06]  * LocutusOfBorg tries to cancel it
[08:10] <LocutusOfBorg> at least I was able to cancel and reschedule
[13:24] <LocutusOfBorg> riscv64-qemu-lgw01-085 is now giving troubles
[13:28] <cjwatson> The VM doesn't seem to be responding to me trying to log into it.  Stuff like "rcu: INFO: rcu_sched detected stalls on CPUs/tasks" on the console
[13:28] <cjwatson> But I have a meeting in two minutes so can't really dig
[13:50] <ginggs> is there a good way to determine from debian/rules if a package is being built on launchpad?
[13:50] <ginggs> e.g. i'd like to reduce parallelism for launchpad builds, but not for local builds
[14:56] <cjwatson> ginggs: There is deliberately no good way.  Shouldn't this sort of thing be sensitive to detected characteristics like CPU count or available memory, rather than to whether it's Launchpad or not?  (After all, the characteristics of Launchpad builders will change over time.)
[14:59] <ginggs> cjwatson: thanks for your answer
[15:01] <ginggs> fwiw, best way of detecting launchpad i came up with so far was checking for 'Launchpad Build Daemon' in SCHROOT_COMMAND
[15:04] <schopin> ginggs: I feel your pain. rustc builds are reduced to -j4 because of similar issues.
[15:05] <ginggs> https://launchpadlibrarian.net/614100106/deal.ii_9.4.0-1_9.4.0-1ubuntu1.diff.gz
[15:06] <ginggs> ^ even varies by architecture :(
[15:23] <cjwatson> ginggs: looking at /CurrentlyBuilding is the more traditional approach, though still not particularly guaranteed
[15:24] <ginggs> cjwatson: thanks, I see some hits on codesearh.debian.net
[15:24] <ginggs> codesearch*
[15:27] <ginggs> wouldn't /CurrentlyBuilding also exist on debian's buildds?
[15:31] <cjwatson> I don't remember, sorry
[15:44] <cjwatson> LocutusOfBorg: I'll just reflash riscv64-qemu-lgw01-085 now, though perhaps the host is having trouble (not sure)
[15:53] <LocutusOfBorg> also 078 maybe...
[15:56] <cjwatson> That one gets me a login: prompt but then seems to be hanging ...
[15:56] <cjwatson> Yeah OK, reflashing
=== remolej5 is now known as remolej
[17:17] <clivejo> cjwatson: Thanks, seems to be working now. 
[17:21] <clivejo> cjwatson: do you still need the auth code in the description?
=== JanC is now known as Guest2803
=== JanC_ is now known as JanC
[20:18] <cjwatson> clivejo: Nope, that was for something ages ago