10:54tomba: I pushed a fix, 3e9a1da270ddff449b1ad9eadc958f43bc204bd2 , to drm-misc-next, thinking that the original commit was not queued for the next merge window, but apparently it was. What's the proper thing to do here, push the fix to drm-misc-fixes too, and live with the duplicate commit? Or is it still drm-misc-next-fixes at this point of time...
13:48phasta: I've got a new feature patch series here that makes an invisible bug visible. I also have a fix for that now. Would it still be the right thing to do to put the fix in misc-fixes and the feature in misc-next? tzimmermann airlied
13:50phasta: because, if I understand the merge plan correctly, fix and feature would then only meet again in Linus's tree
13:51tzimmermann: phasta, that feature series triggers a bug? and you also have a fix for that? you can put the fix into -misc-fixes. as soon as it reaches upstream, we can backmerge into drm-misc-next
13:51tzimmermann: if the bug isn't sever, you can also put everything into drm-misc-next
13:52phasta: tzimmermann: correct
13:52phasta: https://lore.kernel.org/dri-devel/20260414133734.130115-3-phasta@kernel.org/ 13:53phasta: I feel it's probably better to go through misc-next. Otherwise people would see stack traces in misc-next for a while
13:54tzimmermann: yeah, then do that. if the nouveau bug turns out to be critical, we can still cherry-pick as a last resort
13:54phasta: OK, thank you
14:35dschuermann: cwabbott: could you have a look at https://gitlab.freedesktop.org/mesa/mesa/-/jobs/97446938#L2336 ?
14:45DottorLeo: Hi! @daniels about https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/39551 it only affects X11 or even XWayland? Just to understand if something that uses Xwayland like games on Proton are affected
14:45DottorLeo: Thanks!
14:48jannau: phasta: is the mismatch between drm_sched_entity_flush() in the commit messages and drm_sched_entity_kill() in the change intended?
14:52MrCooper: DottorLeo: Xwl in that MR stands for Xwayland
14:57DottorLeo: MrCooper: the present timing extension that was merged while ago also need this MR to work on proton games?
14:58MrCooper: when Proton uses an X display, yes, not when it uses Wayland natively though
15:02phasta: jannau: oh. No it isn't. That's a relic, thx
15:12DottorLeo: thanks!
17:22anholt: valentine: should I expect lava runners to be really network-limited? what I'm seeing is that angle traces run fine on their own (data is pre-downloaded to the rootfs before the replay starts), but if I have downloads through the caching proxy going at the same time, the angle traces take so long to run that they time out sometimes. https://anholt.pages.freedesktop.org/-/mesa/-/jobs/97478972/artifacts/results/index.html success vs
17:22anholt: https://anholt.pages.freedesktop.org/-/mesa/-/jobs/97407377/artifacts/results/index.html fail
17:26anholt: this behavior isn't consistent, but I've seen it happen on both adl and raven, but not yet on a660.
18:02valentine: anholt: not really expected, but I've had suspicions that one of the lava workers (https://lava.collabora.dev/scheduler/worker/lava-rack-sjic-0) has some network issues
18:03valentine: DUTs on that worker can't boot Cuttlefish in time either (CF is super network limited), I've actually just reported the issue earlier today to our lab team
18:03valentine: the failing Raven job you linked was also running on that worker, so pretty sure it's the same issue
18:04valentine: I'm more surprised about the adl runner you mentioned though, since that's on a different worker
18:04valentine: if you hit more instances of this please send over the job links and we can take a closer look.
18:06anholt: I'll try to compile my failing jobs list in a sec