From: ChenQi <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] runqemu: do not check return code of tput
Date: Thu, 11 Apr 2019 14:40:12 +0800 [thread overview]
Message-ID: <0fcf04ce-457c-df87-bd2b-09a7077e654f@windriver.com> (raw)
In-Reply-To: <2e971d062525b21d52a68d1926927f1a60af08d8.1548386264.git.Qi.Chen@windriver.com>
ping
On 01/25/2019 11:18 AM, Chen Qi wrote:
> The subprocess.run was replaced by subprocess.check_call because
> of compatibility support down to python 3.4. But we really don't
> care about whether that command succeeds. Some user reports that
> in some tmux environment, this command fails and gives some
> unpleasant traceback output. So we use 'call' instead of 'check_call'
> to avoid such problem.
>
> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> ---
> scripts/runqemu | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/runqemu b/scripts/runqemu
> index c4a0ca8..d3239ee 100755
> --- a/scripts/runqemu
> +++ b/scripts/runqemu
> @@ -1318,7 +1318,7 @@ def main():
> logger.info("SIGTERM received")
> os.kill(config.qemupid, signal.SIGTERM)
> config.cleanup()
> - subprocess.check_call(["tput", "smam"])
> + subprocess.call(["tput", "smam"])
> signal.signal(signal.SIGTERM, sigterm_handler)
>
> config.check_args()
> @@ -1340,7 +1340,7 @@ def main():
> return 1
> finally:
> config.cleanup()
> - subprocess.check_call(["tput", "smam"])
> + subprocess.call(["tput", "smam"])
>
> if __name__ == "__main__":
> sys.exit(main())
next prev parent reply other threads:[~2019-04-11 6:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 3:18 [PATCH 0/1] runqemu: do not check return code of tput Chen Qi
2019-01-25 3:18 ` [PATCH 1/1] " Chen Qi
2019-04-11 6:40 ` ChenQi [this message]
2019-04-11 20:25 ` Richard Purdie
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=0fcf04ce-457c-df87-bd2b-09a7077e654f@windriver.com \
--to=qi.chen@windriver.com \
--cc=openembedded-core@lists.openembedded.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