patchwork & b4 failing to detect pull request

patchwork & b4 failing to detect pull request

[Conor Dooley]

[-- Attachment #1: Type: text/plain, Size: 580 bytes --]

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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: patchwork & b4 failing to detect pull request

[Konstantin Ryabitsev]

On Thu, Jun 27, 2024 at 03:23:01PM GMT, Conor Dooley wrote:
> 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.

bugbot assign to me

Re: patchwork & b4 failing to detect pull request

[Kernel.org Bugbot]

Hello:

This conversation is now tracked by Kernel.org Bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=218995

There is no need to do anything else, just keep talking.
-- 
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (peebz 0.1)

Re: patchwork & b4 failing to detect pull request

[Kernel.org Bugbot]

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)