From: Steven Rostedt <rostedt@goodmis.org>
To: Russ Dill <Russ.Dill@ti.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ktest.pl: Fix combined usage of BISECT_REVERSE and BISECT_SKIP
Date: Mon, 23 Apr 2012 20:55:15 -0400 [thread overview]
Message-ID: <1335228915.28106.129.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1335222909-14191-1-git-send-email-Russ.Dill@ti.com>
On Mon, 2012-04-23 at 16:15 -0700, Russ Dill wrote:
> When BISECT_REVERSE and BISECT_SKIP are used together with boot or test testing,
> build failures are treated as boot or test failures and 'git bisect bad' is executed instead
> of 'git bisect skip'. This is because the $ret value of -1 is treated as a build failure, but
> the $reverse_bisect logic does not properly handle this.
>
> Simple fix, don't invert $ret if it is -1.
>
> Signed-off-by: Russ Dill <Russ.Dill@ti.com>
> ---
> tools/testing/ktest/ktest.pl | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/ktest/ktest.pl b/tools/testing/ktest/ktest.pl
> index 95d6a6f..5221b00 100755
> --- a/tools/testing/ktest/ktest.pl
> +++ b/tools/testing/ktest/ktest.pl
> @@ -2192,7 +2192,7 @@ sub run_bisect {
> }
>
> # Are we looking for where it worked, not failed?
> - if ($reverse_bisect) {
> + if ($reverse_bisect && $ret != -1) {
Thanks! But can you resend with the following change:
... && $ret >= 0) {
Just incase we have $ret be another negative number for something else.
-- Steve
> $ret = !$ret;
> }
>
next prev parent reply other threads:[~2012-04-24 0:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 23:08 [PATCH] " Russ Dill
2012-04-23 23:15 ` [PATCH v2] ktest.pl: " Russ Dill
2012-04-24 0:55 ` Steven Rostedt [this message]
2012-04-25 3:59 ` Russ Dill
2012-04-25 11:09 ` Steven Rostedt
2012-04-24 2:43 ` [PATCH v3] " Russ Dill
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=1335228915.28106.129.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=Russ.Dill@ti.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®