ChanServ changed the topic of #lima to: Development channel for open source lima driver for ARM Mali4** GPUs - Kernel driver has landed in mainline, userspace driver is part of mesa - Logs at https://oftc.irclog.whitequark.org/lima/
camus has quit [Ping timeout: 480 seconds]
camus has joined #lima
camus1 has quit [Read error: Connection reset by peer]
camus1 has joined #lima
camus has quit [Ping timeout: 480 seconds]
camus has joined #lima
camus1 has quit [Ping timeout: 480 seconds]
Daanct12 has joined #lima
Danct12 has quit [Ping timeout: 480 seconds]
tlwoerner has quit [Remote host closed the connection]
tlwoerner has joined #lima
camus1 has joined #lima
Net147 has joined #lima
camus has quit [Ping timeout: 480 seconds]
Net147 has quit [Quit: Quit]
Net147 has joined #lima
Danct12 has joined #lima
Daanct12 has quit [Ping timeout: 480 seconds]
mripard_ has quit []
mripard has joined #lima
Danct12 has quit [Quit: Quitting]
Net147 has quit [Read error: Connection reset by peer]
Net147 has joined #lima
camus has joined #lima
camus1 has quit [Ping timeout: 480 seconds]
camus1 has joined #lima
camus has quit [Read error: Connection reset by peer]
Danct12 has joined #lima
Net147 has quit [Quit: Quit]
<enunes>
rellla: we have some tests that differ between CI and local runs?
Net147 has joined #lima
camus has joined #lima
camus1 has quit [Ping timeout: 480 seconds]
wwilly has joined #lima
<rellla>
enunes: i guess there is some issue with DIRTY flags
<rellla>
what do the *caselist.txt files in the artifacts mean?
<rellla>
i guess the difference is how i run deqp. i don't use deqp-runner...
<rellla>
dEQP-GLES2.functional.clipping.polygon.multiple_0_viewport_corner for example seems to fail right after the viewport was changed in a wide_line test. i guess i'm missing the viewport again to the original values!?