06:57 <glehmann> what's going on with the a660-vk jobs here? https://gitlab.freedesktop.org/mesa/mesa/-/pipelines/1489071

06:58 <glehmann> are the runners just dead or should I retry?

08:31 <daniels> glehmann: they all took a dive this morning due to an infrastructure issue we're going to solve properly, but are back itmt

09:37 <glehmann> daniels: okay, thanks

09:38 <glehmann> android-angle-venus-anv-cml seems to be retrying often, is this job really good enough for pre merge?

09:48 <daniels> are you seeing that more widely, or just in https://gitlab.freedesktop.org/mesa/mesa/-/jobs/82343934 ?

09:53 <glehmann> I think the MR before (https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/36668) was also mostly waiting for that job to finish

09:54 <glehmann> but I guess n=2 is a small sample size

10:06 <daniels> yeah, looks like one of them is just having an unhealthy day

12:04 <zmike> what is going on with the trace here https://gitlab.freedesktop.org/mesa/mesa/-/jobs/82316128

12:04 <zmike> this thing fails constantly and it looks like it's actually the trace download onto the runner that is failing?

12:27 <daniels> zmike: https://gitlab.freedesktop.org/mesa/piglit/-/merge_requests/1030

12:27 <zmike> ah awesome

12:28 <zmike> been getting spammed by those fails on the daily

17:33 <Mithrandir> emersion: how are we doing on moving to mailman3? gabe is getting very, very long in the tooth and I'd like us to do something about that, but as you know, it needs the mailman 3 migration to complete. I've not been paying much attention for a while, so apologies if there's stuff I should have seen that have passed me by.

17:34 <emersion> Mithrandir: wayland-devel has been migrated to Mailman 3, i wanted to do more but then figured we may want to migrate the DB from SQLite to PostgreSQL

17:34 <emersion> but doing that is not straightforward

17:34 <Mithrandir> agreed, that seems like a wise thing to do

17:34 <emersion> it's essentially a manual process

17:35 <Mithrandir> hmm, that's annoying. :-/ Is it hard or just work (and any idea how much?)

17:35 <emersion> some tools help, but you still need to fixup some stuff manually

17:35 <emersion> and you may miss some stuff and only notice a long time after, when code that uses a field errors out

17:36 <Mithrandir> wow, ok, what kind of wild migration is that? It's not just dumping schema + data and possibly a bit of touch-up and then reloading?

17:36 <emersion> for mailman-web, django can export the DB to a file iirc

17:36 <emersion> https://pgloader.readthedocs.io/en/latest/ref/sqlite.html#migrating-a-sqlite-database-to-postgresql

17:36 <emersion> ^ for mailman core

17:38 <emersion> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/VSU5HDWKJUZQ4ZOKRQS23X6OITSGI2SC/

17:40 <emersion> well, sqlite and psql are pretty different

17:40 <Mithrandir> ok, and since wayland-devel has been migrated, we can't just re-migrate with postgres as the backend?

17:40 <emersion> yeah :/

17:41 <emersion> tbh we might be able to just migrate some basic stuff and not everything

17:41 <emersion> archives are on public-inbox

17:41 <emersion> so we just need to migrate subscribers and list settings, mostly

17:42 <Mithrandir> right, that doesn't seem terribly hard. Somewhat tedious, maybe.

17:42 <emersion> we should purge all archives before migrating because it's just a lot of unencessary data

17:44 <Mithrandir> the last mail to mailman-users linked to above doesn't seem very promising for the sqlite→postgres route… if we have the archive elsewhere, stopping incoming traffic, dumping subscribers and list settings, setting up mailman3 with postgres and recreating the settings and subscribers seems like it would leave us in a more known state?