From: "Kernel.org Bugbot" <bugbot@kernel.org>
To: tools@linux.kernel.org, quic_jjohnson@quicinc.com,
konstantin@linuxfoundation.org, tools@kernel.org
Subject: Re: b4 prep --cleanup failure with cover-strategy: branch-description
Date: Tue, 02 Jul 2024 16:15:11 +0000 [thread overview]
Message-ID: <20240702-b218994c3-89bbe24956f5@bugzilla.kernel.org> (raw)
In-Reply-To: <ca8f8cab-e62c-4784-bdf8-9c92b2c0202c@quicinc.com>
quic_jjohnson writes via Kernel.org Bugzilla:
There is another behavior which I'm also encountering where the b4 prep --cleanup command returns without any backtrace and without apparently doing anything:
[jjohnson:development 1] git checkout b4/md-kvm
Switched to branch 'b4/md-kvm'
[jjohnson:development 2] b4 prep --show-info
branch: b4/md-kvm
cover-subject: md-kvm
base-branch: linux-master
base-commit: 2bfcfd584ff5ccc8bb7acde19b42570414bf880b
start-commit: 2bfcfd584ff5ccc8bb7acde19b42570414bf880b
end-commit: ef5bf7522b9c61da7f935d74246d19bd7e81c71d
series-range: 2bfcfd584ff5ccc8bb7acde19b42570414bf880b..ef5bf7522b9c61da7f935d74246d19bd7e81c71d
change-id: 20240528-md-kvm-36f20bc4a5b0
revision: 3
cover-strategy: branch-description
needs-editing: True
needs-recipients: False
has-prerequisites: False
needs-auto-to-cc: False
needs-checking: False
needs-checking-deps: False
preflight-checks-failing: True
commit-ef5bf7522b9c: KVM: x86: add missing MODULE_DESCRIPTION() macros
series-v2: 2bfcfd584ff5..8e4a790087e7 20240622-md-kvm-v2-1-29a60f7c48b1@quicinc.com
series-v1: 2bfcfd584ff5..5a3a35097cdd 20240528-md-kvm-v1-1-c1b86f0f5112@quicinc.com
[jjohnson:development 3] git checkout md-linux-next-master
Switched to branch 'md-linux-next-master'
[jjohnson:development 4] b4 prep --cleanup b4/md-kvm
[jjohnson:development 5] git branch|fgrep b4/md-kvm
b4/md-kvm
[jjohnson:development 6] git checkout b4/md-kvm
Switched to branch 'b4/md-kvm'
[jjohnson:development 7] b4 prep --show-info
branch: b4/md-kvm
cover-subject: md-kvm
base-branch: linux-master
base-commit: 2bfcfd584ff5ccc8bb7acde19b42570414bf880b
start-commit: 2bfcfd584ff5ccc8bb7acde19b42570414bf880b
end-commit: ef5bf7522b9c61da7f935d74246d19bd7e81c71d
series-range: 2bfcfd584ff5ccc8bb7acde19b42570414bf880b..ef5bf7522b9c61da7f935d74246d19bd7e81c71d
change-id: 20240528-md-kvm-36f20bc4a5b0
revision: 3
cover-strategy: branch-description
needs-editing: True
needs-recipients: False
has-prerequisites: False
needs-auto-to-cc: False
needs-checking: False
needs-checking-deps: False
preflight-checks-failing: True
commit-ef5bf7522b9c: KVM: x86: add missing MODULE_DESCRIPTION() macros
series-v2: 2bfcfd584ff5..8e4a790087e7 20240622-md-kvm-v2-1-29a60f7c48b1@quicinc.com
series-v1: 2bfcfd584ff5..5a3a35097cdd 20240528-md-kvm-v1-1-c1b86f0f5112@quicinc.com
View: https://bugzilla.kernel.org/show_bug.cgi?id=218994#c3
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-07-02 16:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 2:23 b4 prep --cleanup failure with cover-strategy: branch-description Jeff Johnson
2024-06-27 14:23 ` Konstantin Ryabitsev
2024-06-27 14:25 ` Kernel.org Bugbot
2024-07-02 15:55 ` Kernel.org Bugbot
2024-07-02 16:15 ` 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=20240702-b218994c3-89bbe24956f5@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=quic_jjohnson@quicinc.com \
--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).