public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed

From: Martin Jambor <mjambor@suse.cz>
To: GCC Mailing List <gcc@gcc.gnu.org>
Cc: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
Subject: Checks that autotools generated files were re-generated correctly
Date: Mon, 06 Nov 2023 18:04:48 +0100	[thread overview]
Message-ID: <ri6il6e24pb.fsf@> (raw)

Hello,

I have inherited Martin Liška's buildbot script that checks that all
sorts of autotools generated files, mainly configure scripts, were
re-generated correctly when appropriate.  While the checks are hopefully
useful, they report issues surprisingly often and reporting them feels
especially unproductive.

Could such checks be added to our server side push hooks so that commits
introducing these breakages would get refused automatically.  While the
check might be a bit expensive, it only needs to be run on files
touching the generated files and/or the files these are generated from.

Alternatively, Maxim, you seem to have an infrastructure that is capable
of sending email.  Would you consider adding the check to your buildbot
instance and report issues automatically?  The level of totally
false-positives should be low (I thought zero but see
https://gcc.gnu.org/pipermail/gcc-patches/2023-November/635358.html).

Thanks for any ideas which can lead to a mostly automated process.

Martin

next             reply	other threads:[~2023-11-06 17:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 17:04 Martin Jambor [this message]
2023-11-07 22:13 ` Frank Ch. Eigler
2023-11-08 23:30 ` Mark Wielaard
2023-11-15 19:48   ` Mark Wielaard
2023-11-16 18:37     ` Martin Jambor
     [not found] <65491cda.c80a0220.5fa79.7688SMTPIN_ADDED_BROKEN@mx.google.com>
2023-11-06 17:19 ` Christophe Lyon
2023-11-07  7:38   ` Maxim Kuvyrkov
2023-11-07 13:50     ` Carlos O'Donell
2023-11-07 14:36     ` Martin Jambor
     [not found]     ` <654a4b60.2e0a0220.7f3b.6e5aSMTPIN_ADDED_BROKEN@mx.google.com>
2023-11-07 15:42       ` 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=ri6il6e24pb.fsf@ \
    --to=mjambor@suse.cz \
    --cc=gcc@gcc.gnu.org \
    --cc=maxim.kuvyrkov@linaro.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

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).