From: Thomas Schwinge <thomas@codesourcery.com>
To: Mark Wielaard <mark@klomp.org>, <builder@sourceware.org>
Subject: Buildbot 'Blamelist' parsing (was: ☠ Buildbot (Sourceware): gccrust - failed configure (failure) (master))
Date: Tue, 7 Feb 2023 12:43:17 +0100 [thread overview]
Message-ID: <87bkm5em5m.fsf@euler.schwinge.homeip.net> (raw)
In-Reply-To: <20230202224735.6E8B93858C53@sourceware.org>
Hi Mark and team!
A thing I noticed by chance: "something" in the buildbot infrastructure
seems to synthesize supposedly invalid <[...]@sourceware.org> addresses;
for example, see the 'To:' of the parent (original) message:
> To: [...], Cui@sourceware.org, [...], Hu@sourceware.org, [...], bors@sourceware.org, [...]
I'm reasonably sure that at least <bors@sourceware.org> doesn't exist.
;-)
I suppose those recipients are generated out of the 'Blamelist':
On 2023-02-02T22:47:35+0000, builder@sourceware.org wrote:
> Blamelist: [...], Cui,Lili <lili.cui@intel.com>, [...], Hu, Lin1 <lin1.hu@intel.com>, [...], bors[bot] <26634292+bors[bot]@users.noreply.github.com>, [...]
Is there something going wrong with (missing) quoting, "special"
characters like ',' or '[' etc. in the 'display-name'?
Grüße
Thomas
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
next parent reply other threads:[~2023-02-07 11:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230202224735.6E8B93858C53@sourceware.org>
2023-02-07 11:43 ` Thomas Schwinge [this message]
2023-02-07 11:51 ` Thomas Schwinge
2023-02-12 21:21 ` Mark Wielaard
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=87bkm5em5m.fsf@euler.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=builder@sourceware.org \
--cc=mark@klomp.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).