[08:17] <Saviq> sophie I see you managed to reproduce? Did the build I started run out of space? You may have noticed the DNS isn't extra stable there…
[08:24] <Saviq> I cleared some space out on the LXD volume. Note there is shared ccache set up already, on a separate volume
[08:25] <Saviq> Mounted at `/mnt/ccache`
[08:56] <alan_g[m]> Huh?! I thought we dropped this in "cleanup":
[08:56] <alan_g[m]> $ du -sh /snap/mir-test-tools/current/usr/share/doc
[08:56] <alan_g[m]> 9.8M	/snap/mir-test-tools/current/usr/share/doc
[10:01] -GitHub[m]:#mir-server- **[MirServer/ubuntu-frame]** AlanGriffiths opened [pull request #82](https://github.com/MirServer/ubuntu-frame/pull/82): Fix (and simplify) cleanup
[10:01] -GitHub[m]:#mir-server-  
[10:01] -GitHub[m]:#mir-server- > I'm not sure why, but some "cleaned" directories (doc and doc-base) were not removed
[10:59] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths opened [issue #2543](https://github.com/MirServer/mir/issues/2543): miral does not expose wait features based on MainLoop... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/74c3d88504cecb5a8aeed43785503ed1df0ec927)
[13:09] -GitHub[m]:#mir-server- **[MirServer/ubuntu-frame]** bors[bot] edited [pull request #82](https://github.com/MirServer/ubuntu-frame/pull/82): [Merged by Bors] - Fix (and simplify) cleanup
[13:09] -GitHub[m]:#mir-server- **[MirServer/ubuntu-frame]** bors[bot] closed [pull request #82](https://github.com/MirServer/ubuntu-frame/pull/82): [Merged by Bors] - Fix (and simplify) cleanup
[13:42] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths opened [pull request #2544](https://github.com/MirServer/mir/pull/2544): [miral] Improvements to ExternalClientLauncher
[13:42] -GitHub[m]:#mir-server-  
[13:42] -GitHub[m]:#mir-server- > 1. Add a facility to be notified when clients exit
[13:42] -GitHub[m]:#mir-server- > 2. Don't force clients to split command lines themselves
[13:58] <alan_g[m]> @saviq I just noticed we had a pile of PPA builds fail. Before spend time looking into it have you already investigated?
[14:00] <Saviq> alan_g not yet, kinetic/arm64 is the gcc12 bug
[14:00] <Saviq> Some others are infrastructure issues
[14:01] <Saviq> Except for kinetic/amd64, which is a test failure (not seen that one before)
[14:01] <Saviq> And focal/riscv64, which had no logs, so likely infra as well, just restarted
[14:02] <alan_g[m]> I guess we can wait for the next upload before getting too interested
[14:03] <Saviq> That.
[14:04] <Saviq> Had you a look at all the snap rebuilds… again? Is that what triggered your `doc` cleanup?
[14:05] <alan_g[m]> Yes. And https://forum.snapcraft.io/t/outdated-contains-outdated-ubuntu-packages/31205
[14:06] <alan_g[m]> I was poking through the snaps to see what was actually affected and noticed
[15:58] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths opened [pull request #2545](https://github.com/MirServer/mir/pull/2545): Delete obsolete workaround
[16:37] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths edited [pull request #2544](https://github.com/MirServer/mir/pull/2544): [miral] Improvements to ExternalClientLauncher
[16:37] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths edited [pull request #2544](https://github.com/MirServer/mir/pull/2544): [miral] Improvement to ExternalClientLauncher
[16:37] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths marked [pull request #2544](https://github.com/MirServer/mir/pull/2544): [miral] Improvement to ExternalClientLauncher as ready for review
[19:37] -GitHub[m]:#mir-server- **[MirServer/mir]** wmww marked [pull request #2508](https://github.com/MirServer/mir/pull/2508): Bump wl_seat to v8 and implement hi-res scrolling as ready for review
[19:47] <sophie-w> Mir in the armhf VM took forever to build yesterday, and by the time I finally got it built was distracted by other stuff. Now back. I reproduced, but main seems to also be broken. Since CI isn't generally broken right now, I suspect there's some persistent state that's causing mmap to fail. I don't know how to reboot the VM, but that would be the next step.
[20:10] <Saviq> sophie: if you think it's kernel state, just exit the container and reboot