All of lore.kernel.org
 help / color / mirror / Atom feed
From: gregkh at linuxfoundation.org (Greg KH)
Subject: [Linux-kernel-mentees] Testing stable-rc v5.1.17-rc1-g57f5b343c
Date: Fri, 5 Jul 2019 11:17:21 +0200	[thread overview]
Message-ID: <20190705091721.GA22725@kroah.com> (raw)
In-Reply-To: <20190705081141.GA17898@arch>

On Fri, Jul 05, 2019 at 01:41:41PM +0530, Amol Surati wrote:
> Hi,
> 
> Given that 5.1.17-rc1 is marked on the stable-rc repo, I attempted to
> carry out the required 'stable release contribution' task, ahead, in
> anticipation of receiving the stable-review email.
> 
> Running kselftest (as root) showed the errors displayed below.
> 
> Are these an indication of problems, in my environment, which I must
> fix? Or are some of the failures meant to be ignored?

Do you get the same errors when running 5.1.16?  Try doing that on a
"known good" release first to get your testing system set up properly.

> The 'lkmp stable release contribution' wiki isn't quite clear on what
> needs to be done with kselftest result if there are failures in it.
> 
> Upon checking one of the logs of a test result from linaro - 
> https://lkft.validation.linaro.org/scheduler/job/806628 - it is found
> that certain tests, that fail on my side, either succeed or are marked
> as skipped, on their side.

Some tests are skipped because of various reasons, as you are finding
out :)

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: gregkh@linuxfoundation.org (Greg KH)
Subject: [Linux-kernel-mentees] Testing stable-rc v5.1.17-rc1-g57f5b343c
Date: Fri, 5 Jul 2019 11:17:21 +0200	[thread overview]
Message-ID: <20190705091721.GA22725@kroah.com> (raw)
Message-ID: <20190705091721.ZnFYmx3Doi-09d3xcaVpr0mmfSjN8i9X3Ytw9Elencg@z> (raw)
In-Reply-To: <20190705081141.GA17898@arch>

On Fri, Jul 05, 2019 at 01:41:41PM +0530, Amol Surati wrote:
> Hi,
> 
> Given that 5.1.17-rc1 is marked on the stable-rc repo, I attempted to
> carry out the required 'stable release contribution' task, ahead, in
> anticipation of receiving the stable-review email.
> 
> Running kselftest (as root) showed the errors displayed below.
> 
> Are these an indication of problems, in my environment, which I must
> fix? Or are some of the failures meant to be ignored?

Do you get the same errors when running 5.1.16?  Try doing that on a
"known good" release first to get your testing system set up properly.

> The 'lkmp stable release contribution' wiki isn't quite clear on what
> needs to be done with kselftest result if there are failures in it.
> 
> Upon checking one of the logs of a test result from linaro - 
> https://lkft.validation.linaro.org/scheduler/job/806628 - it is found
> that certain tests, that fail on my side, either succeed or are marked
> as skipped, on their side.

Some tests are skipped because of various reasons, as you are finding
out :)

thanks,

greg k-h

  reply	other threads:[~2019-07-05  9:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-05  8:11 [Linux-kernel-mentees] Testing stable-rc v5.1.17-rc1-g57f5b343c suratiamol
2019-07-05  8:11 ` Amol Surati
2019-07-05  9:17 ` gregkh [this message]
2019-07-05  9:17   ` Greg KH
2019-07-05 10:22   ` suratiamol
2019-07-05 10:22     ` Amol Surati

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=20190705091721.GA22725@kroah.com \
    --to=unknown@example.com \
    /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.