ci/traces: Skip poor performant traces
What does this MR do and why?
Skip poor performant traces
Some traces are not reaching the 10 FPS mark. Let's remove them because
they make traces-performance jobs longer and are not useful
for the end-user atm.
Leave the respective traces YAML documented with it, so eventually, if the performance of the affected driver becomes better for other traces. We may reenable them.
Table of affected traces:
| job_name | trace_name | Median FPS |
|---|---|---|
| iris-apl-traces-performance | gputest/furmark-v2.trace | 9.23 |
| iris-apl-traces-performance | gputest/pixmark-volplosion-v2.trace | 6.83 |
| iris-glk-traces-performance | gputest/furmark-v2.trace | 6.06 |
| iris-glk-traces-performance | gputest/pixmark-volplosion-v2.trace | 4.11 |
| zink-tu-a618-traces-performance | gputest/pixmark-piano-v2.trace | 1.26 |
| zink-tu-a618-traces-performance | gputest/pixmark-volplosion-v2.trace | 6.68 |
| zink-tu-a618-traces-performance | ror/ror-default.trace | 8.60 |