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 joined #lima
camus has quit [Remote host closed the connection]
camus has joined #lima
dllud_ has joined #lima
dllud has quit [Read error: Connection reset by peer]
dllud has joined #lima
dllud_ has quit [Read error: Connection reset by peer]
Daanct12 has joined #lima
Danct12 has quit [Ping timeout: 480 seconds]
Daaanct12 has joined #lima
Daaanct12 has quit [Quit: Quitting]
Daanct12 has quit [Ping timeout: 480 seconds]
Danct12 has joined #lima
<rellla>
enunes: do you have your piglit command line options and excludes somewhere available? im trying to set it up now
megi1 has quit []
megi has joined #lima
dllud_ has joined #lima
dllud has quit [Read error: Connection reset by peer]
<enunes>
if you are looking at the test I mentioned in your latest MR, maybe it's best to just remove all exclude-tests and add something like: -t '^spec@arb_clip_control'
<enunes>
then if you look at the summary it gives the command and env vars to run the test directly so you dont even need to run the piglit runner
<rellla>
enunes: thanks for that. i have a working setup now and will give main branch a chance.
<rellla>
what is the reason why you exclude the single spec@ tests? do they crash?
<enunes>
yes those are the ones that still dmesg-fail or dmesg-warn :)
<enunes>
the negative-index ones are probably not a hard fix
<rellla>
ok. i will do a full run now with your excludes first, then have a look at clipcontrol. results will appear here http://lima.imkreisrum.de in the future :)
wwilly has quit [Ping timeout: 480 seconds]
wwilly has joined #lima
dllud has joined #lima
dllud_ has quit [Read error: Connection reset by peer]