00:03 jenatali: glehmann: Ok trying to retrofit this into the DXIL backend is going to be a massive pain. I really need a nir instruction that's u32 unpacking to f32
00:03 jenatali: Otherwise I need to store effectively an f16 SSA value but pretend that it's u32 and I don't have a great way to do that
00:08 ngcortes: anholt, is there a way to have deqp-runner generate its own caselist? eg if I want to test gles on glcts, can I just have it generate a caselist based on all the KHR-GLES xml files?
09:02 rcv11x: Hello everyone, I have a question about the commit search filter. How can I filter to see what will be included in Mesa 26.0? https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests
09:07 K900: You can't
09:07 K900: You can look at https://gitlab.freedesktop.org/mesa/mesa/-/tree/staging/26.0?ref_type=heads
09:18 glehmann: jenatali: okay, I pushed a version that adds a dxil specific unpack opcode
09:19 glehmann: could share it with r600, but meh
10:22 eric_engestrom: ngcortes: deqp itself (not deqp-runner) has `--deqp-runmode=txt-caselist` which dumps the list of all the tests compiled in
10:28 eric_engestrom: (there's also `--deqp-runmode=stdout-caselist` if you want to use it in a script and don't want to have to keep a mapping of the file name for each deqp binary)
10:39 daniels: mupuf, eric_engestrom: all the Steam Decks are having a bad time
10:40 mupuf: daniels: thanks for letting me know, looking into it
10:40 daniels: https://gitlab.freedesktop.org/mesa/mesa/-/jobs/92030823 on -7, https://gitlab.freedesktop.org/mesa/mesa/-/jobs/92030824 on -5, https://gitlab.freedesktop.org/mesa/mesa/-/jobs/92030825 on -4, https://gitlab.freedesktop.org/mesa/mesa/-/jobs/92030826 on -2
10:40 eric_engestrom: they're all idle
10:40 eric_engestrom: thanks, I was typing to ask for links ^^
10:40 eric_engestrom: this is really weird
10:41 daniels: though possibly transient as they did eventually come back it seems, just too late to not tank the pipeline
10:41 eric_engestrom: mupuf: should I restart the executor?
10:41 eric_engestrom: oh, not touching, if it's back
10:41 eric_engestrom: better to leave as is for possible investigation
10:41 daniels: wfm
10:41 mupuf: seems like a gitlab runner issue, not executor :s
10:42 eric_engestrom: this feels like a network interruption between the farm and internet
10:42 daniels: if it falls down a well again, I'll let you know
10:42 daniels: sounds right yeah
10:42 eric_engestrom: daniels: thanks!
10:42 eric_engestrom: mupuf: agreed, but the executor is the one carrying the messages, that's why I was thinking it might be that
10:43 eric_engestrom: s/messages/job log/
10:43 mupuf: eric_engestrom: what do you mean? No, the gitlab runner is the one communicating with gitlab
10:43 eric_engestrom: oh, directly? I misremembered then
10:43 mupuf: yeah :)
10:43 eric_engestrom: ack, thanks ^^