All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chris Paterson" <chris.paterson2@renesas.com>
To: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
	"alice.ferrazzi@miraclelinux.com"
	<alice.ferrazzi@miraclelinux.com>
Subject: Re: [cip-dev] Kselftest implementation
Date: Tue, 13 Apr 2021 22:27:01 +0000	[thread overview]
Message-ID: <OSAPR01MB23856FC69ACA82D31DBE9519B74F9@OSAPR01MB2385.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <CANgtXuP5wVfj7x_ef=oSV6S80zMnAG4JPa_N_W4hNUAE7qmHQA@mail.gmail.com>

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

Hello Alice,

> From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On
> Behalf Of Alice Ferrazzi via lists.cip-project.org
> Sent: 13 April 2021 18:30
> 
> Hi everyone,
> 
> I'm Alice Ferrazzi from Cybertrust Japan.
> 
> I'm currently working on adding Kselftest to the current CIP CI tests of linux-
> cip Kernel

Thank you for your work on this!

> 
> I made and tested kselftest on a testing instance of lava, currently tested
> only on qemu x86_64

If you'd like to test on a wider range of platforms then get in touch and we'll get you access to the CIP LAVA instance.

> I implemented a simple skiplist in the kselftest envelope for skipping tests
> that are currently not working.
> The usage is similar to how spectre-meltdown-checker-test is currently
> working.
> 
> Raw log:
> 
> http://140.211.166.173:10080/scheduler/job/329
> Results list:
> http://140.211.166.173:10080/results/329/1_kselftest

It looks like a great start.

>
> 
> My idea is to start implementing kselftest tests for at least qemu x86_64
> architecture and expand in the future to other architectures.
> As Iwamatsu-san pointed, we need also to create kselftest binary.
> 
> I'm currently thinking of implementing kselftest binary creation mechanism
> on linux-cip-ci kernel build script but I still didn't start to work on this yet.
> 
> Kselftest test code:
> 
> https://gitlab.com/alice.ferrazzi/cip-kselftest

Is there any work we can leverage from the Linaro test-definitions repo?
https://github.com/Linaro/test-definitions/tree/master/automated/linux/kselftest

KernelCI also recently implemented kselftest support if that's useful at all, this'll include the build side of things.
https://github.com/kernelci/kernelci-core/tree/main/config/lava/kselftest

>
> 
> linux-cip Kernel Kselftest implementation (currently in draft):
> https://gitlab.com/cip-project/cip-testing/linux-cip-ci/-/merge_requests

Please assign the MR to me when you're ready for it to be reviewed, or if you need any help.

Also let me know if you want write access to the linux-cip-ci repo.
If you push your branch to our repo directly the CI will be able to run, making it easier for you to test.

Kind regards, Chris

>
> 
> Thanks,
> Alice
> --
> 
> ======================================
> Cybertrust Japan Co.,Ltd.
> Alice Ferrazzi
> alice.ferrazzi@miraclelinux.com <mailto:alice.ferrazzi@miraclelinux.com>
> ======================================


[-- Attachment #2: Type: text/plain, Size: 428 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6375): https://lists.cip-project.org/g/cip-dev/message/6375
Mute This Topic: https://lists.cip-project.org/mt/82071182/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/4520388/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


  reply	other threads:[~2021-04-13 22:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-13 17:29 [cip-dev] Kselftest implementation Alice Ferrazzi
2021-04-13 22:27 ` Chris Paterson [this message]
2021-04-15  2:04   ` Alice Ferrazzi
2021-04-22  7:34     ` Nobuhiro Iwamatsu
2021-04-23  8:49       ` Alice Ferrazzi

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=OSAPR01MB23856FC69ACA82D31DBE9519B74F9@OSAPR01MB2385.jpnprd01.prod.outlook.com \
    --to=chris.paterson2@renesas.com \
    --cc=alice.ferrazzi@miraclelinux.com \
    --cc=cip-dev@lists.cip-project.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.