We are currently experiencing downtime impacting viewing & cloning the Mesa repo, and some GitLab pages returning 503. Please see #freedesktop on IRC for more updates.

Commit f7aae05d authored by Alexandros Frantzis's avatar Alexandros Frantzis

Misc. improvements to README.md

Signed-off-by: Alexandros Frantzis's avatarAlexandros Frantzis <alexandros.frantzis@collabora.com>
parent 96c6c471
Tracie - Traces Continuous Integration System
==============================================
Tracie - Mesa Traces Continuous Integration System
==================================================
Home for the Mesa CI effort.
Prototype phase.
Home of the Mesa trace testing effort prototype.
## CI internals
### Docker image setup
The Mesa CI prototype is run inside a specially prepared docker image. The
image contains the latest dependencies needed to build Mesa and also the tools
for trace replay (currently apitrace and renderdoc).
The Mesa trace testing prototype is run inside a specially prepared docker
image. The image contains the latest dependencies needed to build Mesa and also
the tools for trace replay (currently apitrace and renderdoc).
Image setup uses helpers from the debian.yml template from
https://gitlab.freedesktop.org/wayland/ci-templates. This template is included
by the Mesa CI yaml file.
by our own yaml file.
The code to setup the image is based on the respective code from the Mesa
repository and resides in:
[gitlab-ci/debian-install.sh](gitlab-ci/debian-install.sh)
[.gitlab-ci/debian-install.sh](.gitlab-ci/debian-install.sh)
The images are cached based on the image tag, so any changes to to the install
script should be accompanied by a change to the `DEBIAN_TAG` variable in
......@@ -44,9 +43,9 @@ CI runs by using the `TRACES_DB_REPO` and `TRACES_DB_COMMIT` CI variables.
### Replaying traces
Mesa CI uses a set of scripts to replay traces and check the output against the
reference images. We currently replay the traces with software rendering under
the Xvfb X server.
Mesa traces CI uses a set of scripts to replay traces and check the output
against the reference images. We currently replay the traces with software
rendering under the Xvfb X server.
The [scripts/dump_trace_images.py](scripts/dump_trace_images.py) script replays
traces, dumping the images from calls in the replay that match the expected
......@@ -86,7 +85,7 @@ The [scripts/diff_trace_images.py](scripts/diff_trace_images.py) script depends
on a recent version of apitrace being in the path.
For some guidance for building apitrace and renderdoc, check the
[gitlab-ci/debian-install.sh](gitlab-ci/debian-install.sh) script.
[gitlab-ci/debian-install.sh](.gitlab-ci/debian-install.sh) script.
To ensure python3 can find the renderdoc python module you need to set
`PYTHONPATH` to point to the location of `renderdoc.so` (binary python modules)
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment