From: Hoa Nguyen Date: Sat, 29 Aug 2020 09:35:11 +0000 (-0700) Subject: ext: Force testlib to only create one Log object X-Git-Tag: v20.1.0.0~69 X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=c207628d1e45741f3874286b3177d5cc00204ead;p=gem5.git ext: Force testlib to only create one Log object Log object should remain being a singleton throughout the program. The current code creates multiple Log objects, which at least causes the issues of missing outputs in stdout. E.g., "Logging call to command", which logs which command is being called in a subprocess, is missing from stdout. Change-Id: I96c5dd79c4f14e0a013c15d42d202397488d56b6 Signed-off-by: Hoa Nguyen Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/33715 Tested-by: kokoro Reviewed-by: Bobby R. Bruce Reviewed-by: Jason Lowe-Power Maintainer: Jason Lowe-Power --- diff --git a/ext/testlib/runner.py b/ext/testlib/runner.py index 7425e795d..a59aca3a4 100644 --- a/ext/testlib/runner.py +++ b/ext/testlib/runner.py @@ -77,7 +77,8 @@ class TestParameters(object): def __init__(self, test, suite): self.test = test self.suite = suite - self.log = log.Log(test) + self.log = log.test_log + self.log.test = test @helper.cacheresult def _fixtures(self):