From: Philip Li <philip.li@intel.com>
To: lkp@lists.01.org
Subject: Re: livepatching selftests failure on current master branch
Date: Thu, 06 Jun 2019 08:49:43 +0800 [thread overview]
Message-ID: <20190606004943.GA30795@intel.com> (raw)
In-Reply-To: <e264efb1-0b6e-c860-7a6d-ce92bde8efa2@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1607 bytes --]
On Wed, Jun 05, 2019 at 10:51:53AM -0400, Joe Lawrence wrote:
> On 6/5/19 10:31 AM, Philip Li wrote:
> >On Wed, Jun 05, 2019 at 09:48:02AM -0400, Joe Lawrence wrote:
> >>On 5/17/19 10:17 AM, Miroslav Benes wrote:
> >>>Hi,
> >>>
> >>>I noticed that livepatching selftests fail on our master branch
> >>>(https://git.kernel.org/pub/scm/linux/kernel/git/livepatching/livepatching.git/).
> >>>
> >>>...
> >>
> >>[ adding lkp(a)01.org to this email ]
> >>
> >>lkp folks, I was wondering if the kernel selftests were included as
> >>part of the test-bot and if so, do we need to do anything specific
> >yes, kernel selftest is part of regular execution, which includes the livepatching
> > test. Also the livepatching.git is under our testing...
>
> Hi Philip,
>
> Good to hear. My github tree and Josh's kernel.org tree are
> included as (perhaps other livepatching dev trees as well), so the
> more coverage the better :)
>
> > ... But we may not successfully
> >bisect all failures.
>
> That's okay, though I guess I'm not clear why there wasn't an email
> reporting that the livepatching selftests failed after
> livepatching.git was recently updated to include tglx's stack trace
> fixes.
>
> Do the tests only run for unique commits (ie, will it skip when
> livepatching.git updates/merges latest linux tree ??)
it will not skip, though we are not testing commit by commit. If the issue
is found, and bisect to the bad commit, we will report to author of that
commit for information.
>
> Thanks,
>
> -- Joe
next prev parent reply other threads:[~2019-06-06 0:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 14:17 livepatching selftests failure on current master branch Miroslav Benes
2019-05-17 14:30 ` Joe Lawrence
2019-06-05 13:48 ` Joe Lawrence
2019-06-05 14:31 ` Philip Li
2019-06-05 14:51 ` Joe Lawrence
2019-06-06 0:49 ` Philip Li [this message]
2019-06-06 18:43 ` Joe Lawrence
2019-06-10 14:36 ` Philip Li
2019-06-11 7:42 ` Petr Mladek
2019-06-14 6:55 ` Philip Li
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=20190606004943.GA30795@intel.com \
--to=philip.li@intel.com \
--cc=lkp@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.