15:33 <john-cabaj[m]> <nukelet[m]> "btw, i prepared a 6.12.0-1005-..." <- Gonna try testing this today nukelet . Do you have a link to the source tree?

15:38 <john-cabaj[m]> <john-cabaj[m]> "Gonna try testing this today..." <- Also, could you copy the binaries to Noble?

16:21 <nukelet[m]> <john-cabaj[m]> "Gonna try testing this today..." <- sure thing

16:21 <nukelet[m]> linux-main: https://git.launchpad.net/~vpeixoto/+git/linux-asahi-arm

16:21 <nukelet[m]> linux-meta: https://git.launchpad.net/~vpeixoto/+git/linux-meta-asahi-arm

16:24 <nukelet[m]> also copied the binaries to oracular/noble, waiting for them to be published

16:25 <nukelet[m]> tobhe[m]: wow the arm64 builders are still having issues?

16:25 <nukelet[m]> or is it just the fallout from the last incident

16:26 <tobhe[m]> I have a build waiting for 17h now...

16:32 <Paul[m]> <tobhe[m]> "I have a build waiting for 17h..." <- So I guess just 2 hours left at the maximum?

16:32 <tobhe[m]> I think there are issues with the datacenter that hosts the arm builders so the estimate is probably not accurate

16:33 <tobhe[m]> one of the reasons why it still hasn't built is that last time it was scheduled it failed after a few minutes because of some random timeout

16:34 <tobhe[m]> the launchpad team is aware of the issue 🙂

16:35 <Paul[m]> I wonder why so many builders are in the Cleaning step

16:35 <Paul[m]> https://arc.net/l/quote/djnlqjul

16:35 <Paul[m]> s/djnlqjul/bwxklidr/

16:36 <tobhe[m]> yeah that seems to be related

16:36 <tobhe[m]> maybe just wrong status reporting

16:37 <Paul[m]> Got you