09:31 <alatiera> DavidHeidelberg[m] yea it was probably downloading the image that took a while

09:58 <bentiss> daniels: FYI, making progress on the repolication of the cluster. I had to restart it twice (third time's the charm as they say) to understand that by default it tried to fit ~40 TB in a single disk of 7 TB... And specifying before-hand the pg_num (placement group number) to the same value than the old cluster makes things work

09:58 <bentiss> so now, I have replicated opa and harbor (and keeping them in sync), and I just started the main fdo-s3 one

10:05 <mupuf> bentiss: \o/

10:08 <daniels> bentiss: oooh

17:47 <dcbaker> I'm running into issues with zink jobs failing to launch on the 23.2 stable branches: https://gitlab.freedesktop.org/mesa/mesa/-/jobs/46938412. Is this a known issue, or am I missing a patch?

18:18 <DavidHeidelberg[m]> dcbaker: Infra error, this shouldn't be related to the code

18:19 <DavidHeidelberg[m]> retriggered the job, we'll see

18:19 <dcbaker> David Heidelberg: cool, I just kept seeing over and over and wanted to make sure there wasn't a host name change or something like that

18:32 <__tim> in mesa, do windows images often get rebuilt even on e.g. small code changes?

18:33 <__tim> e.g. looking at https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/24551/pipelines, the bottom pipeline in the list, there are two windows image rebuilds, 55 + 82 mins

18:33 <__tim> is that expected?

18:34 <__tim> (fork pipeline)

18:39 <DavidHeidelberg[m]> dcbaker: hmm, something is bad on LAVA side, the file can be downloaded on my machine, but download not working there. I reported, but that's all I can do for now

21:19 <jenatali> __tim: They shouldn't, only when an image tag is changed