ci: TRACES_DB_PATH and RESULTS_PATH defined as relative paths
authorPablo Saavedra <psaavedra@igalia.com>
Tue, 5 May 2020 07:07:34 +0000 (09:07 +0200)
committerMarge Bot <eric+marge@anholt.net>
Mon, 18 May 2020 17:27:42 +0000 (17:27 +0000)
commiteb1f22fb014384bec96fa2c2b08e09a2cb29cddd
tree517314a4847966c3d557496c30172b3ed48bd6f7
parent78c46c2126109dc5c1cb2ff315aecdd69b93d1f5
ci: TRACES_DB_PATH and RESULTS_PATH defined as relative paths

RESULTS_PATH and RESULTS_PATH, as variables in the module context, are
resolved one single time, only during the first module loading. If the
the Python code in execution changes the current dir at some point,
those paths are not going to be updated anymore keeping the paths
wrongly pointing to the old working dir.

This change modify the definition of those variables to use simply
relative paths.

Signed-off-by: Pablo Saavedra <psaavedra@igalia.com>
Reviewed-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>
Reviewed-by: Andres Gomez <agomez@igalia.com>
Reviewed-by: Rohan Garg <rohan.garg@collabora.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4916>
.gitlab-ci/tracie/tracie.py