From: Gabe Black <gabeblack@google.com>
Date: Thu, 22 Nov 2018 01:35:28 +0000 (-0800)
Subject: systemc: Run the systemc tests with the CWD in the build directory.
X-Git-Tag: v19.0.0.0~1359
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=e186f870896f9b32a324958f0fa06e45c79c0534;p=gem5.git

systemc: Run the systemc tests with the CWD in the build directory.

This will prevent some (but not all) output files the tests generate
from ending up outside the build directory. Because some output file
streams are constructed as global objects, their paths are resolved
relative to the CWD when gem5 starts, before the config script has a
chance to change it.

Subsequent changes will make verify.py should make gem5 start with the
correct working directory, cleaning up the remaining leaking files.

Change-Id: I75a1256719dab4c98ab868c209d09b9dcdabb458
Reviewed-on: https://gem5-review.googlesource.com/c/14518
Reviewed-by: Gabe Black <gabeblack@google.com>
Maintainer: Gabe Black <gabeblack@google.com>
---

diff --git a/src/systemc/tests/verify.py b/src/systemc/tests/verify.py
index 87c5d127e..c9ede77a0 100755
--- a/src/systemc/tests/verify.py
+++ b/src/systemc/tests/verify.py
@@ -165,7 +165,7 @@ class RunPhase(TestPhaseBase):
                 '--quiet',
                 config_path,
                 '--working-dir',
-                os.path.dirname(test.src_dir())
+                os.path.dirname(test.dir())
             ])
             # Ensure the output directory exists.
             if not os.path.exists(test.m5out_dir()):