From: "Kernel.org Bugbot" <bugbot@kernel.org>
To: tools@linux.kernel.org, konstantin@linuxfoundation.org,
tools@kernel.org, conor@kernel.org, arnd@arndb.de
Subject: Re: patchwork & b4 failing to detect pull request
Date: Fri, 28 Jun 2024 08:30:13 +0000 [thread overview]
Message-ID: <20240628-b218995c2-e8b4d683465f@bugzilla.kernel.org> (raw)
In-Reply-To: <20240627-unrest-rigid-c7bb9ac94bc7@spud>
zhaomzhao writes via Kernel.org Bugzilla:
(In reply to Bugbot from comment #0)
> Conor Dooley <conor@kernel.org> writes:
>
> Yo,
>
> Neither of the following two PRs
> https://lore.kernel.org/all/20240419-unnamable-tapering-f05a0af759e3@spud/
> https://lore.kernel.org/all/20240627-wobbly-custody-5df564133088@spud/
> appear in the soc patchwork at
> https://patchwork.kernel.org/project/linux-soc/list/
> ?submitter=206274&state=%2A&archive=both,
> and `b4 pr 20240627-wobbly-custody-5df564133088@spud` fails too.
>
> It seems the trailing + in the tag, while accepted by git, could be
> the problem? At least, all other PRs that I have sent do not have a + in
> them and have been processed without a problem.
>
> Thanks,
> Conor.
>
> (via https://msgid.link/20240627-unrest-rigid-c7bb9ac94bc7@spud)
Hi, the root cause is the + sign, please try modify this file with the following patch:
vim /usr/local/lib/python3.9/site-packages/b4/pr.py
--- a/src/b4/pr.py
+++ b/src/b4/pr.py
@@ -38,7 +38,8 @@ PULL_BODY_WITH_COMMIT_ID_RE = [
# I don't like these
PULL_BODY_REMOTE_REF_RE = [
- re.compile(r'^\s*([\w+-]+(?:://|@)[\w/.@:~-]+)[\s\\]+([\w/._-]+)\s*$', re.M | re.I),
+ # match string like: "https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/ riscv-dt-fixes-for-v6.10-rc5+"
+ re.compile(r'^\s*([\w+-]+(?:://|@)[\w/.@:~-]+)[\s\\]+([\w/._+-]+)\s*$', re.M | re.I),
re.compile(r'^\s*([\w+-]+(?:://|@)[\w/.@~-]+)\s*$', re.M | re.I),
]
View: https://bugzilla.kernel.org/show_bug.cgi?id=218995#c2
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (peebz 0.1)
prev parent reply other threads:[~2024-06-28 8:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 14:23 patchwork & b4 failing to detect pull request Conor Dooley
2024-06-27 14:55 ` Konstantin Ryabitsev
2024-06-27 15:00 ` Kernel.org Bugbot
2024-06-28 8:30 ` Kernel.org Bugbot [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=20240628-b218995c2-e8b4d683465f@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=arnd@arndb.de \
--cc=conor@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=tools@kernel.org \
--cc=tools@linux.kernel.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 NNTP newsgroup(s).