Lines Matching defs:traces
20 - Replay of application traces
55 Application traces replay
58 The CI replays application traces with various drivers in two different jobs. The first
59 job replays traces listed in ``src/<driver>/ci/traces-<driver>.yml`` files and if any
60 of those traces fail the pipeline fails as well. The second job replays traces listed in
61 ``src/<driver>/ci/restricted-traces-<driver>.yml`` and it is allowed to fail. This second
63 has been granted access to these traces.
65 A traces YAML file also includes a ``download-url`` pointing to a MinIO
66 instance where to download the traces from. While the first job should always work with
67 publicly accessible traces, the second job could point to an url with restricted access.
69 Restricted traces are those that have been made available to Mesa developers without a
72 contributors without permissions to download non-redistributable traces can be merged
75 As an aside, only maintainers of such non-redistributable traces are responsible for
80 non-redistributable traces can request permission to Daniel Stone <daniels@collabora.com>.
82 gitlab.freedesktop.org accounts that are to be granted access to these traces will be