05:57 mareko: how do I upgrade libdrm in CI? this doesn't seem to be enough: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/26643/diffs?commit_id=4d34229497150793ee1442ff3288fec6395dc324
06:10 mareko: daniels: ^^
08:13 daniels: mareko: .gitlab-ci/image-tags.yaml
10:34 mareko: I'm just gonna do it like 4d38890c9e7b6c5aba750fe13d25d1bcb9b0a6f4
14:53 daniels: mareko: I’m not near my laptop, but just bump all the non-Windows tags
16:27 karolherbst: quick ci review? I'm merging debian-rusticl-testing into debian-testing: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/26807 should make CI a bit cheaper on the CPU runner side :)
19:40 mareko: daniels: I did this, but it didn't help: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/26643/diffs?commit_id=42fbe83f77a64d13b33101e8523795291b45803f
19:40 mareko: bnieuwenhuizen: ^^
20:34 Lynne: so after launching OpenGothic and loading a level, hardware gets stuck in a loop consuming 100% of time even after exiting
20:34 Lynne: not sure where to report this odd issue, but mesa seems like a good place as it's what tell hardware what to do
20:35 Lynne: radeontop shows only the "Clip Rectangle" units being used, which tells me it's likely stuck doing dumb math
20:49 Lynne: it could be mesh shader related, as the engine uses it, and afaik dxvk is its only other user
20:52 daniels: mareko: looks like 848f59deda3ae7bb99409a3d15ddafe96b763ea1 removed the building of libdrm as it was now unnecessary, so you'd have to reintroduce the parts which called build-libdrm from the rootfs scripts and remove the install calls from apt
20:53 Lynne: yup, it's mesh shader related
20:54 Lynne: Venemo: do you know who to ping or could you try to replicate this?
20:54 mareko: daniels: do I need to bump the tag again after that?
20:54 mareko: *tags
20:57 daniels: mareko: yeah, sorry
21:19 mareko: DavidHeidelberg: is this good? https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/26643/diffs?commit_id=77f6498029a070ded3af812509e66b1df3a51f9c if not, can you please make it good?
21:38 DavidHeidelberg: mareko: on the phone, look workable. I was REALLY hoping we won't get back to hacking libdrm in again and use snapshot package but as I see... Here we go again.
21:39 DavidHeidelberg: karolherbst: lgtm
22:03 robclark: DavidHeidelberg: tbh, we should treat libdrm as special and not make it part of container build to make things like what mareko is trying to do easier.. since it takes like no time to build and it isn't completely unusual for mesa to depend on a libdrm change
22:27 jenatali: robclark: That does mean that CI jobs could run into issues with the external project, e.g. having network problems. Having it embedded in the container means that Mesa's CI only depends on the Mesa repo and the containers in the common case
22:27 jenatali: Though I guess libdrm is also FDO so maybe that's not a real concern
22:31 robclark: yeah, I figure if we have trouble cloning libdrm then all is already lost ;-)
22:32 robclark: I guess llvm is maybe a thing that needs to bump alongside mesa sometimes, but not as frequently.. so probably ok just to treat libdrm as the one special case
23:07 jenatali: Yeah you don't want to build/install LLVM in a regular build job, that definitely belongs in a contaoner