All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Li <philip.li@intel.com>
To: lkp@lists.01.org
Subject: Re: livepatching selftests failure on current master branch
Date: Wed, 05 Jun 2019 22:31:17 +0800	[thread overview]
Message-ID: <20190605143117.GC19267@intel.com> (raw)
In-Reply-To: <c3a528e2-40f1-5a3d-38d7-6acb188bbd88@redhat.com>

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

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. But we may not successfully
bisect all failures.

The mails related to livepatching test or livepatch  in last two months are

https://lists.01.org/pipermail/lkp/2019-April/010026.html
https://lists.01.org/pipermail/lkp/2019-May/010218.html

Thanks

> to include the livepatching selftests?
> 
> Thanks,
> 
> -- Joe
> _______________________________________________
> LKP mailing list
> LKP(a)lists.01.org
> https://lists.01.org/mailman/listinfo/lkp

  reply	other threads:[~2019-06-05 14:31 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 [this message]
2019-06-05 14:51     ` Joe Lawrence
2019-06-06  0:49       ` Philip Li
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=20190605143117.GC19267@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.