From: Jun Dong <junx.dong@intel.com>
To: dts@dpdk.org
Cc: lijuan.tu@intel.com, qingx.sun@intel.com, junx.dong@intel.com
Subject: [PATCH V1] framework/logger: fix bug of generate the log output path
Date: Wed, 20 Apr 2022 15:04:20 +0800 [thread overview]
Message-ID: <20220420070420.3574-1-junx.dong@intel.com> (raw)
First, the log default path was generated based main script's directory.
When modifying the standard project, we moved main script from framework
sub directory to base directory, but no synchronous change the log patch
generate rule. This patch fixed it.
Signed-off-by: Jun Dong <junx.dong@intel.com>
---
framework/logger.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/framework/logger.py b/framework/logger.py
index 576a51dc..774ab9c4 100644
--- a/framework/logger.py
+++ b/framework/logger.py
@@ -194,7 +194,7 @@ class DTSLOG(BaseLoggerAdapter):
self.debug_lvl = logging.DEBUG
if log_dir is None:
- self.log_path = os.getcwd() + "/../" + FOLDERS["Output"]
+ self.log_path = os.getcwd() + "/" + FOLDERS["Output"]
else:
self.log_path = (
log_dir # log dir should contain tag/crb global value and mod in dts
--
2.25.1
next reply other threads:[~2022-04-20 7:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 7:04 Jun Dong [this message]
2022-04-20 7:54 ` lijuan.tu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220420070420.3574-1-junx.dong@intel.com \
--to=junx.dong@intel.com \
--cc=dts@dpdk.org \
--cc=lijuan.tu@intel.com \
--cc=qingx.sun@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).