Subject: Re: [REGRESSION] kselftest: next-20200915

From: Shuah Khan <[email-masked]>
Date: Tue, 15 Sep 2020 14:18:40 -0600

On 9/15/20 11:52 AM, Justin Cook wrote:
> Hello,
> 
> Linaro had previously been sending out a report based on our testing of 
> the linux kernel using kselftest. We paused sending that report to fix a 
> few issues. We are now continuing the process, starting with this report.
> 
> If you have any questions, comments, feedback, or concerns please email 
> [email-masked] <mailto:[email-masked]>.
> 
> Thanks,
> 
> Justin
> 

Hi Justin,

Thanks for the report. It would be nice to see the reports. However, it
is hard for me to determine which tests failed and why.

> On Tue, 15 Sep 2020 at 12:44, LKFT <[email-masked] 
> <mailto:[email-masked]>> wrote:
> 
>     ## Kernel
>     * kernel: 5.9.0-rc5
>     * git repo:
>     ['https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git',
>     'https://gitlab.com/Linaro/lkft/mirrors/next/linux-next']
>     * git branch: master
>     * git commit: 6b02addb1d1748d21dd1261e46029b264be4e5a0
>     * git describe: next-20200915
>     * Test details:
>     https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20200915
> 
>     ## Regressions (compared to build next-20200914)
> 
>     juno-r2:
>        kselftest:
>          * memfd_memfd_test
> 
>     x86:
>        kselftest-vsyscall-mode-native:
>          * kvm_vmx_preemption_timer_test

I looked for the above two failures to start with since these
are regressions and couldn't find them.

Are the regressions tied to new commits in linux-next from the
mm and kvm trees?

thanks,
-- Shuah