public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: Christophe Lyon <christophe.lyon@linaro.org>
To: Simon Marchi <simark@simark.ca>
Cc: buildbot@sourceware.org
Subject: Re: [PATCH 3/6] autoregen.py: Flush all print commands
Date: Mon, 15 Apr 2024 13:55:30 +0200	[thread overview]
Message-ID: <CAPS5khbriq64zNXgC2iwokEu+b43JO6YmXDniiJKiEJMhONpDg@mail.gmail.com> (raw)
In-Reply-To: <1aedfffb-f027-474c-af36-d9053cb9a078@simark.ca>

On Mon, 15 Apr 2024 at 04:09, Simon Marchi <simark@simark.ca> wrote:
>
>
>
> On 2024-04-12 16:05, Christophe Lyon wrote:
> > For consistency and easier debug of traces
> > ---
> >  builder/containers/autoregen.py | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/builder/containers/autoregen.py b/builder/containers/autoregen.py
> > index 6e341e2..c52a524 100755
> > --- a/builder/containers/autoregen.py
> > +++ b/builder/containers/autoregen.py
> > @@ -56,7 +56,7 @@ AUTORECONF_DIRS = [
> >  #
> >  # Print the command on stdout prior to running it.
> >  def run_shell(cmd: str):
> > -    print(f"+ {cmd}")
> > +    print(f"+ {cmd}", flush=True)
> >      res = subprocess.run(
> >          f"{cmd}",
> >          shell=True,
> > @@ -105,7 +105,7 @@ run_shell(f"{AUTOMAKE_BIN} --version")
> >  run_shell(f"{ACLOCAL_BIN} --version")
> >  run_shell(f"{AUTOHEADER_BIN} --version")
> >
> > -print(f"Extra environment: {EXTRA_ENV}")
> > +print(f"Extra environment: {EXTRA_ENV}", flush=True)
> >
> >  config_folders: list[Path] = []
> >  repo_root = Path.cwd()
>
> Can you clarify when/where/why that's needed?  I would expect the stdout
> stream to be flushed when there is an end-of-line (which print() does).
>

I'm not quite sure now.... I think I was annoyed when looking at
builds in progress on the sourceware buildbot.

> Simon

  reply	other threads:[~2024-04-15 11:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-12 20:05 [PATCH 0/6] autoregen.py: Improve support for GCC Christophe Lyon
2024-04-12 20:05 ` [PATCH 1/6] auroregen.py: Check AC_CONFIG_MACRO_DIR instead of AC_CONFIG_MACRO_DIRS Christophe Lyon
2024-04-12 20:05 ` [PATCH 2/6] autoregen.py: Move comment Christophe Lyon
2024-04-12 20:05 ` [PATCH 3/6] autoregen.py: Flush all print commands Christophe Lyon
2024-04-15  2:09   ` Simon Marchi
2024-04-15 11:55     ` Christophe Lyon [this message]
2024-04-12 20:05 ` [PATCH 4/6] autoregen.py: Use autoreconf in most GCC directories Christophe Lyon
2024-04-15  3:07   ` Simon Marchi
2024-04-15 12:52     ` Christophe Lyon
2024-04-15 14:48       ` Simon Marchi
2024-04-16 14:47         ` Christophe Lyon
2024-04-16 15:32           ` Simon Marchi
2024-04-16 16:12             ` Christophe Lyon
2024-04-17 14:30       ` Christophe Lyon
2024-04-15 11:42   ` Mark Wielaard
2024-04-15 12:46     ` Mark Wielaard
2024-04-15 12:56       ` Christophe Lyon
2024-04-12 20:05 ` [PATCH 5/6] autoregen.py: Add support for autogen Christophe Lyon
2024-04-12 20:05 ` [PATCH 6/6] autoregen.py: Add binutils directories to AUTORECONF_DIRS Christophe Lyon
2024-04-14 22:33 ` [PATCH 0/6] autoregen.py: Improve support for GCC Mark Wielaard
2024-04-15 11:52   ` Christophe Lyon

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=CAPS5khbriq64zNXgC2iwokEu+b43JO6YmXDniiJKiEJMhONpDg@mail.gmail.com \
    --to=christophe.lyon@linaro.org \
    --cc=buildbot@sourceware.org \
    --cc=simark@simark.ca \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).