From eb1f22fb014384bec96fa2c2b08e09a2cb29cddd Mon Sep 17 00:00:00 2001 From: Pablo Saavedra Date: Tue, 5 May 2020 09:07:34 +0200 Subject: [PATCH] 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 Reviewed-by: Alexandros Frantzis Reviewed-by: Andres Gomez Reviewed-by: Rohan Garg Part-of: --- .gitlab-ci/tracie/tracie.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.gitlab-ci/tracie/tracie.py b/.gitlab-ci/tracie/tracie.py index 92ff9c200c3..d1a1c563021 100644 --- a/.gitlab-ci/tracie/tracie.py +++ b/.gitlab-ci/tracie/tracie.py @@ -16,8 +16,8 @@ from urllib import parse import dump_trace_images -TRACES_DB_PATH = os.getcwd() + "/traces-db/" -RESULTS_PATH = os.getcwd() + "/results/" +TRACES_DB_PATH = "./traces-db/" +RESULTS_PATH = "./results/" def replay(trace_path, device_name): success = dump_trace_images.dump_from_trace(trace_path, [], device_name) -- 2.30.2