public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: buildbot@sourceware.org
Subject: Re: [PATCH] Add binutils-gdb-autoregen builder
Date: Sun, 12 Nov 2023 18:19:12 +0100	[thread overview]
Message-ID: <20231112171912.GO31613@gnu.wildebeest.org> (raw)
In-Reply-To: <ZVECB_5PCtf2FW4R@elastic.org>

Hi Frank,

On Sun, Nov 12, 2023 at 11:49:11AM -0500, Frank Ch. Eigler wrote:
> > Generalize the autoregen.py script by searching for 'configure.ac'
> > instead of 'configure'. Skip "foreign" readline and minizip dirs.
> > Make autoregen_step and git_diff_step generic, define early.
> > Add binutils-gdb-autoregen builder to binutils_gdb_scheduler.
> 
> > +autoregen_step = steps.ShellCommand(
> > +        command="autoregen.py",
> > +        name="autoregen.py",
> > +        haltOnFailure=True)
> 
> Note that this stuff literally can only add work for the developers.
> If the tooling knows what the output purportedly should be, it is in a
> position to correct the mismatches, not merely complain about it.
> That would actually save human effort.

The build step does generate a diff that when applies makes sure the
files are regenerated with the correct version of the tools. The
buildbots however don't have write access, so cannot apply and push
the patch itself.

The container can also be used to generate the same locally, see
https://inbox.sourceware.org/20231112171138.1553448-1-mark@klomp.org/T/

So it could also be done through some other mechanism which has direct
write access to the git repro. But you'll have to negotiate with the
projects to see if they want that.

Cheers,

Mark

      reply	other threads:[~2023-11-12 17:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-12 16:19 Mark Wielaard
2023-11-12 16:49 ` Frank Ch. Eigler
2023-11-12 17:19   ` Mark Wielaard [this message]

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=20231112171912.GO31613@gnu.wildebeest.org \
    --to=mark@klomp.org \
    --cc=buildbot@sourceware.org \
    --cc=fche@elastic.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).