All of lore.kernel.org
 help / color / mirror / Atom feed
From: keescook at chromium.org (Kees Cook)
Subject: next-20190510 kselftest results
Date: Sat, 11 May 2019 07:51:32 -0700	[thread overview]
Message-ID: <201905110746.D6C85E86F6@keescook> (raw)
In-Reply-To: <359070592.29.1557569697898.JavaMail.jenkins@db10df53eddc>

On Sat, May 11, 2019 at 10:14:57AM +0000, ci_notify at linaro.org wrote:
> Summary
> ------------------------------------------------------------------------
> kernel: 5.1.0
> git repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git branch: master
> git commit: a802303934b3bd4df6e2fc8bf2e4ebced1c37556
> git describe: next-20190510
> Test details: https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20190510
> 
> Regressions (compared to build next-20190509)
> ------------------------------------------------------------------------
> No regressions                                                                                                          
>                                                                                                                        
> Fixes (compared to build next-20190509)                                                                   
> ------------------------------------------------------------------------                                               
> No fixes
> 
> In total:
> ------------------------------------------------------------------------
> Ran 12 total tests in the following environments and test suites.
> pass 11
> fail 1
> xfail 0
> skip 0
> 
> Environments
> --------------
> - dragonboard-410c - arm64
> - hi6220-hikey - arm64
> - i386
> - juno-r2 - arm64
> - qemu_arm
> - qemu_arm64
> - qemu_i386
> - qemu_x86_64
> - x15 - arm
> - x86_64
> 
> Test Suites
> -----------
> * boot-lkft-kselftests-master-519

What counts as a "pass" for this? I looked at the x86_64 log, and there are lots of kselftest failures, but the dashboard counts it as a "pass"?

$ wget https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20190510/testrun/716064/log
$ grep '^ok ' log | wc -l
60
$ grep '^not ok' log | grep -iv '# SKIP' | wc -l
30
$ grep -i '^not ok.*# SKIP' log | wc -l
18

60 pass, 30 fail, 18 skip

-- 
Kees Cook

WARNING: multiple messages have this Message-ID (diff)
From: keescook@chromium.org (Kees Cook)
Subject: next-20190510 kselftest results
Date: Sat, 11 May 2019 07:51:32 -0700	[thread overview]
Message-ID: <201905110746.D6C85E86F6@keescook> (raw)
Message-ID: <20190511145132.ieCf_zu7E53NgZx5OoGO4fMBQU5oW10HPpcLk4Ek8L0@z> (raw)
In-Reply-To: <359070592.29.1557569697898.JavaMail.jenkins@db10df53eddc>

On Sat, May 11, 2019@10:14:57AM +0000, ci_notify@linaro.org wrote:
> Summary
> ------------------------------------------------------------------------
> kernel: 5.1.0
> git repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git branch: master
> git commit: a802303934b3bd4df6e2fc8bf2e4ebced1c37556
> git describe: next-20190510
> Test details: https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20190510
> 
> Regressions (compared to build next-20190509)
> ------------------------------------------------------------------------
> No regressions                                                                                                          
>                                                                                                                        
> Fixes (compared to build next-20190509)                                                                   
> ------------------------------------------------------------------------                                               
> No fixes
> 
> In total:
> ------------------------------------------------------------------------
> Ran 12 total tests in the following environments and test suites.
> pass 11
> fail 1
> xfail 0
> skip 0
> 
> Environments
> --------------
> - dragonboard-410c - arm64
> - hi6220-hikey - arm64
> - i386
> - juno-r2 - arm64
> - qemu_arm
> - qemu_arm64
> - qemu_i386
> - qemu_x86_64
> - x15 - arm
> - x86_64
> 
> Test Suites
> -----------
> * boot-lkft-kselftests-master-519

What counts as a "pass" for this? I looked at the x86_64 log, and there are lots of kselftest failures, but the dashboard counts it as a "pass"?

$ wget https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20190510/testrun/716064/log
$ grep '^ok ' log | wc -l
60
$ grep '^not ok' log | grep -iv '# SKIP' | wc -l
30
$ grep -i '^not ok.*# SKIP' log | wc -l
18

60 pass, 30 fail, 18 skip

-- 
Kees Cook

  reply	other threads:[~2019-05-11 14:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-11 10:14 next-20190510 kselftest results ci_notify
2019-05-11 10:14 ` ci_notify
2019-05-11 14:51 ` keescook [this message]
2019-05-11 14:51   ` Kees Cook
2019-05-14 15:28   ` anders.roxell
2019-05-14 15:28     ` Anders Roxell
2019-05-14 15:46     ` keescook
2019-05-14 15:46       ` Kees Cook
2019-05-14 21:49       ` anders.roxell
2019-05-14 21:49         ` Anders Roxell

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=201905110746.D6C85E86F6@keescook \
    --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.