From mboxrd@z Thu Jan 1 00:00:00 1970 From: suratiamol at gmail.com (Amol Surati) Date: Fri, 5 Jul 2019 15:52:54 +0530 Subject: [Linux-kernel-mentees] Testing stable-rc v5.1.17-rc1-g57f5b343c In-Reply-To: <20190705091721.GA22725@kroah.com> References: <20190705081141.GA17898@arch> <20190705091721.GA22725@kroah.com> Message-ID: <20190705102254.GA22194@arch> List-Id: On Fri, Jul 05, 2019 at 11:17:21AM +0200, Greg KH wrote: > 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. Okay, I am building 5.1.6, to use it to calibrate the system. I think that the two kselftest test-runs, one on each build, will match each other in behaviour closely. Thanks, amol > > > 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: suratiamol@gmail.com (Amol Surati) Date: Fri, 5 Jul 2019 15:52:54 +0530 Subject: [Linux-kernel-mentees] Testing stable-rc v5.1.17-rc1-g57f5b343c In-Reply-To: <20190705091721.GA22725@kroah.com> References: <20190705081141.GA17898@arch> <20190705091721.GA22725@kroah.com> Message-ID: <20190705102254.GA22194@arch> List-Id: Content-Type: text/plain; charset="UTF-8" Message-ID: <20190705102254.IvkyrD8PDYzHTa3j8ztwRzFnTyZMcgqHZHSIU_sVgvQ@z> On Fri, Jul 05, 2019 at 11:17:21AM +0200, Greg KH wrote: > 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. Okay, I am building 5.1.6, to use it to calibrate the system. I think that the two kselftest test-runs, one on each build, will match each other in behaviour closely. Thanks, amol > > > 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