From: James Prestwood <prestwoj@gmail.com>
To: iwd@lists.01.org
Subject: [PATCH v2] test-runner: fix duplicate process output
Date: Tue, 02 Mar 2021 08:30:29 -0800 [thread overview]
Message-ID: <20210302163029.1980263-1-prestwoj@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2518 bytes --]
Process output was being duplicated when -v was used. This was
due to both stderr and stdout being appended to the write_fd list
as well as stderr being set to stdout in the Popen call.
To fix this only stdout should be appended to the write_fd list,
but then there comes a problem with closing the streams. stdout
cannot be closed, so instead it is special cased. A new
verbose boolean was added to Process which, if True, will
cause any output to be written to stdout explicitly.
---
tools/test-runner | 14 ++++++++++----
1 file changed, 10 insertions(+), 4 deletions(-)
v2:
* Added check for self.verbose so long running
processes get an IO watch and can actually
print to the console with -v.
diff --git a/tools/test-runner b/tools/test-runner
index eab0f0ab..a0c4022e 100755
--- a/tools/test-runner
+++ b/tools/test-runner
@@ -174,6 +174,7 @@ class Process:
self.write_fds = []
self.io_watch = None
self.cleanup = cleanup
+ self.verbose = False
if not namespace:
self.output_name = '/tmp/%s-out' % self.name
@@ -195,8 +196,7 @@ class Process:
if ctx:
# Verbose requested, add stdout/stderr to write FD list
if self.name in ctx.args.verbose:
- self.write_fds.append(sys.__stdout__)
- self.write_fds.append(sys.__stderr__)
+ self.verbose = True
# Add output file to FD list
if outfile:
@@ -230,11 +230,11 @@ class Process:
# the process is being waited for, the log/outfile bits
# will be handled after the process exists.
#
- if self.write_fds != [] and not wait and not check:
+ if self.write_fds != [] and not wait and not check or self.verbose:
self.io_watch = GLib.io_add_watch(self.stdout, GLib.IO_IN,
self.io_callback)
- self.pid = subprocess.Popen(self.args, stdout=self.stdout, stderr=subprocess.STDOUT,
+ self.pid = subprocess.Popen(self.args, stdout=self.stdout, stderr=self.stdout,
env=env, cwd=os.getcwd())
print("Starting process {}".format(self.pid.args))
@@ -261,6 +261,9 @@ class Process:
self.write_fds = []
+ if self.verbose:
+ sys.__stdout__.write(self.out)
+
print("%s returned %d" % (args[0], self.ret))
if check and self.ret != 0:
raise subprocess.CalledProcessError(returncode=self.ret, cmd=self.args)
@@ -284,6 +287,9 @@ class Process:
for f in self.write_fds:
f.write(data)
+ if self.verbose:
+ sys.__stdout__.write(data)
+
return True
def __del__(self):
--
2.26.2
next reply other threads:[~2021-03-02 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 16:30 James Prestwood [this message]
2021-03-02 16:38 ` [PATCH v2] test-runner: fix duplicate process output Denis Kenzior
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=20210302163029.1980263-1-prestwoj@gmail.com \
--to=prestwoj@gmail.com \
--cc=iwd@lists.01.org \
/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