From: "Nikolai Kondrashov" <Nikolai.Kondrashov@redhat.com> To: Hanjun Guo <guohanjun@huawei.com>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Scott Branden <scott.branden@broadcom.com> Cc: Huxinwei <huxinwei@huawei.com>, LKML <linux-kernel@vger.kernel.org>, Yanjin <yanjin.yan@huawei.com>, BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>, Zhaohongjiang <zhaohongjiang@huawei.com>, "Zhangdianfang (Dianfang, OS Lab)" <zhangdianfang@huawei.com>, PEIXIN HOU <PEIXIN.HOU@huawei.com>, Linux ARM <linux-arm-kernel@lists.infradead.org>, kernelci@groups.io, Wei Yongjun <weiyongjun1@huawei.com>, Lijinyue <lijinyue@huawei.com> Subject: Re: 5.10 LTS Kernel: 2 or 6 years? Date: Fri, 26 Feb 2021 13:21:57 +0200 [thread overview] Message-ID: <a8518d24-8b02-39f7-d4e3-82c28715191d@redhat.com> (raw) In-Reply-To: <4abea94d-5232-19ab-3139-569e485403b3@huawei.com> Hi Hanjun, On 2/26/21 10:03 AM, Hanjun Guo wrote: > On 2021/2/19 22:45, Nikolai Kondrashov wrote: >> Would you be interested in working with the Linux Foundation KernelCI project >> on submitting your build and test results to the common database - KCIDB? > > Yes, we are willing to sent the test results to KCIDB. Wonderful! > For now, all the tests are inside the company, which blocks us to > directly sent the test results out of the test machine due to the > security policy, it takes us sometime to discuss how to send out > the test results, and we may need do the test in a public cloud. I understand. We faced the same dilemma at Red Hat with the CKI project, where I'm employed. In the end we just decided to publish the logs from the test lab (most sensitive part, I suppose) as they are, but then Red Hat is already a very open company. Here's an example of all logs we publish for a revision: https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/02/22/624489 And here's that revision in KCIDB: https://staging.kernelci.org:3000/d/revision/revision?orgId=1&var-dataset=kernelci04&var-id=093ae67c90a629599a0cb2300c5686ec7d8bbdd0 Take your time, there is a range of solutions to choose from, starting from isolating your test machines/boards, to running the test in the public cloud as you mention. Although the latter lacks the benefit of testing your own hardware, of course. Please also note that we require the tested kernel's code to be publicly available to accept results. >> We are working on aggregating results from various testing systems so we can >> provide a dashboard, and a single, aggregated e-mail report to subscribed >> maintainers and developers. >> >> We have a prototype dashboard at https://staging.kernelci.org:3000/ and are >> working hard on making the e-mail reports good enough to start reaching out to >> maintainers. >> >> We already have ARM, Google Syzbot, Gentoo GKernelCI, Red Hat CKI, and, of >> course, KernelCI native tests sending data to the database. Linaro Tuxsuite is >> starting sending today. We could use your data, and of course any development >> help you could spare :) > > How can we connect to the KCIDB? Can we send the test data out by email > first? The simplest way would be using our "kcidb-submit" command-line tool. Here's a minimal example of sending an empty report: echo '{"version":{"major":3,"minor":0}}' | kcidb-submit -p kernelci-production -t kernelci_new Another way could be using our Python 3 library, which is a little more involved. Here's an example sending the same empty report in Python: import kcidb client = kcidb.Client(project_id="kernelci-production", topic_name="kernelci_new") client.submit({"version":{"major":3,"minor":0}}) Finally, you can send (validated) data using the Google Cloud Pub/Sub service directly, using the library in one of the supported languages: https://cloud.google.com/pubsub/docs/tutorials The latter would be the least stable option (change-wise), but something e.g. Google Syzbot is already using. See more details in our Submission HOWTO: https://github.com/kernelci/kcidb/blob/main/SUBMISSION_HOWTO.md Although email submissions are theoretically possible (with due authentication, setup, etc.), they're not currently supported, and we would not put them at the top of our (rather large) priority list. Topmost item being getting the data we already have to developers. Would be excited to have you on board! Nick On 2/26/21 10:03 AM, Hanjun Guo wrote: > Hi Nick, > > Sorry for taking so long to reply you, we had discussions on how to > corporate with KCIDB, please see my comments inline. > > On 2021/2/19 22:45, Nikolai Kondrashov wrote: >> Hi Hanjun, >> >> On 2/19/21 10:54 AM, Hanjun Guo wrote: >> > In specific, we will start from the testing work, using HULK robot >> > (reports lots of bugs to mainline kernel) testing framework to test >> > compile, reboot, functional testing, and will extend to basic >> > performance regression testing in the future. >> >> I heard about Huawei ramping up kernel testing from someone at FOSDEM >> 2019. I wonder if it was you :) Nice to see your progress and the company >> stepping up to help with testing! > > I Cced Yongjun and Jinyue, they are the key persons :) > >> >> Would you be interested in working with the Linux Foundation KernelCI project >> on submitting your build and test results to the common database - KCIDB? > > Yes, we are willing to sent the test results to KCIDB. > > For now, all the tests are inside the company, which blocks us to > directly sent the test results out of the test machine due to the > security policy, it takes us sometime to discuss how to send out > the test results, and we may need do the test in a public cloud. > >> >> We are working on aggregating results from various testing systems so we can >> provide a dashboard, and a single, aggregated e-mail report to subscribed >> maintainers and developers. >> >> We have a prototype dashboard at https://staging.kernelci.org:3000/ and are >> working hard on making the e-mail reports good enough to start reaching out to >> maintainers. >> >> We already have ARM, Google Syzbot, Gentoo GKernelCI, Red Hat CKI, and, of >> course, KernelCI native tests sending data to the database. Linaro Tuxsuite is >> starting sending today. We could use your data, and of course any development >> help you could spare :) > > How can we connect to the KCIDB? Can we send the test data out by email > first? > >> >> I wish I could show you my today's KCIDB presentation at DevConf.cz, but the >> recording is not out yet. Meanwhile you can take a look at our presentation at >> last year's Linux Plumbers: https://youtu.be/y9Glc90WUN0?t=10739 >> >> Or see our intro in an older blog post: >> https://foundation.kernelci.org/blog/2020/08/21/introducing-common-reporting/ >> >> Anyone wishing to contribute to KCIDB gets credentials and permissions to >> submit to our "playground" setup where they can send their data, see it in a >> dashboard, experiment without worrying about breaking anything, and decide if >> they like it or n > >> If you're interested, take a look at our Submission HOWTO: >> https://github.com/kernelci/kcidb/blob/v8/SUBMISSION_HOWTO.md >> and send an email to kernelci@groups.io (CC'd), or come over to the #kernelci >> channel on freenode.net! > > Thanks! > Hanjun
WARNING: multiple messages have this Message-ID (diff)
From: Nikolai Kondrashov <Nikolai.Kondrashov@redhat.com> To: Hanjun Guo <guohanjun@huawei.com>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Scott Branden <scott.branden@broadcom.com> Cc: Yanjin <yanjin.yan@huawei.com>, LKML <linux-kernel@vger.kernel.org>, kernelci@groups.io, Huxinwei <huxinwei@huawei.com>, BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>, Zhaohongjiang <zhaohongjiang@huawei.com>, "Zhangdianfang \(Dianfang, OS Lab\)" <zhangdianfang@huawei.com>, Wei Yongjun <weiyongjun1@huawei.com>, Lijinyue <lijinyue@huawei.com>, PEIXIN HOU <PEIXIN.HOU@huawei.com>, Linux ARM <linux-arm-kernel@lists.infradead.org> Subject: Re: 5.10 LTS Kernel: 2 or 6 years? Date: Fri, 26 Feb 2021 13:21:57 +0200 [thread overview] Message-ID: <a8518d24-8b02-39f7-d4e3-82c28715191d@redhat.com> (raw) In-Reply-To: <4abea94d-5232-19ab-3139-569e485403b3@huawei.com> Hi Hanjun, On 2/26/21 10:03 AM, Hanjun Guo wrote: > On 2021/2/19 22:45, Nikolai Kondrashov wrote: >> Would you be interested in working with the Linux Foundation KernelCI project >> on submitting your build and test results to the common database - KCIDB? > > Yes, we are willing to sent the test results to KCIDB. Wonderful! > For now, all the tests are inside the company, which blocks us to > directly sent the test results out of the test machine due to the > security policy, it takes us sometime to discuss how to send out > the test results, and we may need do the test in a public cloud. I understand. We faced the same dilemma at Red Hat with the CKI project, where I'm employed. In the end we just decided to publish the logs from the test lab (most sensitive part, I suppose) as they are, but then Red Hat is already a very open company. Here's an example of all logs we publish for a revision: https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/02/22/624489 And here's that revision in KCIDB: https://staging.kernelci.org:3000/d/revision/revision?orgId=1&var-dataset=kernelci04&var-id=093ae67c90a629599a0cb2300c5686ec7d8bbdd0 Take your time, there is a range of solutions to choose from, starting from isolating your test machines/boards, to running the test in the public cloud as you mention. Although the latter lacks the benefit of testing your own hardware, of course. Please also note that we require the tested kernel's code to be publicly available to accept results. >> We are working on aggregating results from various testing systems so we can >> provide a dashboard, and a single, aggregated e-mail report to subscribed >> maintainers and developers. >> >> We have a prototype dashboard at https://staging.kernelci.org:3000/ and are >> working hard on making the e-mail reports good enough to start reaching out to >> maintainers. >> >> We already have ARM, Google Syzbot, Gentoo GKernelCI, Red Hat CKI, and, of >> course, KernelCI native tests sending data to the database. Linaro Tuxsuite is >> starting sending today. We could use your data, and of course any development >> help you could spare :) > > How can we connect to the KCIDB? Can we send the test data out by email > first? The simplest way would be using our "kcidb-submit" command-line tool. Here's a minimal example of sending an empty report: echo '{"version":{"major":3,"minor":0}}' | kcidb-submit -p kernelci-production -t kernelci_new Another way could be using our Python 3 library, which is a little more involved. Here's an example sending the same empty report in Python: import kcidb client = kcidb.Client(project_id="kernelci-production", topic_name="kernelci_new") client.submit({"version":{"major":3,"minor":0}}) Finally, you can send (validated) data using the Google Cloud Pub/Sub service directly, using the library in one of the supported languages: https://cloud.google.com/pubsub/docs/tutorials The latter would be the least stable option (change-wise), but something e.g. Google Syzbot is already using. See more details in our Submission HOWTO: https://github.com/kernelci/kcidb/blob/main/SUBMISSION_HOWTO.md Although email submissions are theoretically possible (with due authentication, setup, etc.), they're not currently supported, and we would not put them at the top of our (rather large) priority list. Topmost item being getting the data we already have to developers. Would be excited to have you on board! Nick On 2/26/21 10:03 AM, Hanjun Guo wrote: > Hi Nick, > > Sorry for taking so long to reply you, we had discussions on how to > corporate with KCIDB, please see my comments inline. > > On 2021/2/19 22:45, Nikolai Kondrashov wrote: >> Hi Hanjun, >> >> On 2/19/21 10:54 AM, Hanjun Guo wrote: >> > In specific, we will start from the testing work, using HULK robot >> > (reports lots of bugs to mainline kernel) testing framework to test >> > compile, reboot, functional testing, and will extend to basic >> > performance regression testing in the future. >> >> I heard about Huawei ramping up kernel testing from someone at FOSDEM >> 2019. I wonder if it was you :) Nice to see your progress and the company >> stepping up to help with testing! > > I Cced Yongjun and Jinyue, they are the key persons :) > >> >> Would you be interested in working with the Linux Foundation KernelCI project >> on submitting your build and test results to the common database - KCIDB? > > Yes, we are willing to sent the test results to KCIDB. > > For now, all the tests are inside the company, which blocks us to > directly sent the test results out of the test machine due to the > security policy, it takes us sometime to discuss how to send out > the test results, and we may need do the test in a public cloud. > >> >> We are working on aggregating results from various testing systems so we can >> provide a dashboard, and a single, aggregated e-mail report to subscribed >> maintainers and developers. >> >> We have a prototype dashboard at https://staging.kernelci.org:3000/ and are >> working hard on making the e-mail reports good enough to start reaching out to >> maintainers. >> >> We already have ARM, Google Syzbot, Gentoo GKernelCI, Red Hat CKI, and, of >> course, KernelCI native tests sending data to the database. Linaro Tuxsuite is >> starting sending today. We could use your data, and of course any development >> help you could spare :) > > How can we connect to the KCIDB? Can we send the test data out by email > first? > >> >> I wish I could show you my today's KCIDB presentation at DevConf.cz, but the >> recording is not out yet. Meanwhile you can take a look at our presentation at >> last year's Linux Plumbers: https://youtu.be/y9Glc90WUN0?t=10739 >> >> Or see our intro in an older blog post: >> https://foundation.kernelci.org/blog/2020/08/21/introducing-common-reporting/ >> >> Anyone wishing to contribute to KCIDB gets credentials and permissions to >> submit to our "playground" setup where they can send their data, see it in a >> dashboard, experiment without worrying about breaking anything, and decide if >> they like it or n > >> If you're interested, take a look at our Submission HOWTO: >> https://github.com/kernelci/kcidb/blob/v8/SUBMISSION_HOWTO.md >> and send an email to kernelci@groups.io (CC'd), or come over to the #kernelci >> channel on freenode.net! > > Thanks! > Hanjun _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-02-26 11:21 UTC|newest] Thread overview: 133+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-25 19:55 5.10 LTS Kernel: 2 or 6 years? Scott Branden 2021-01-25 19:55 ` Scott Branden 2021-01-26 2:50 ` Adam Borowski 2021-01-26 2:50 ` Adam Borowski 2021-01-26 7:29 ` Greg Kroah-Hartman 2021-01-26 7:29 ` Greg Kroah-Hartman 2021-01-26 17:35 ` Florian Fainelli 2021-01-26 17:35 ` Florian Fainelli 2021-01-26 18:30 ` Scott Branden 2021-01-26 18:30 ` Scott Branden 2021-01-26 18:51 ` Greg Kroah-Hartman 2021-01-26 18:51 ` Greg Kroah-Hartman 2021-01-26 20:15 ` Willy Tarreau 2021-01-26 20:15 ` Willy Tarreau 2021-01-29 10:00 ` 10 years -- was " Pavel Machek 2021-02-17 9:40 ` Greg Kroah-Hartman 2021-02-17 9:40 ` Greg Kroah-Hartman 2021-02-17 19:48 ` Scott Branden 2021-02-17 19:48 ` Scott Branden 2021-02-18 7:43 ` Greg Kroah-Hartman 2021-02-18 7:43 ` Greg Kroah-Hartman 2021-02-18 11:31 ` Willy Tarreau 2021-02-18 11:31 ` Willy Tarreau 2021-02-18 14:15 ` Jari Ruusu 2021-02-18 14:15 ` Jari Ruusu 2021-02-18 14:29 ` Greg Kroah-Hartman 2021-02-18 14:29 ` Greg Kroah-Hartman 2021-02-18 20:55 ` Pavel Machek 2021-02-18 20:55 ` Pavel Machek 2021-02-18 22:43 ` Ondrej Zary 2021-02-18 22:43 ` Ondrej Zary 2021-02-19 8:00 ` Pavel Machek 2021-02-19 8:00 ` Pavel Machek 2021-02-19 8:30 ` Greg Kroah-Hartman 2021-02-19 8:30 ` Greg Kroah-Hartman 2021-02-18 14:33 ` Willy Tarreau 2021-02-18 14:33 ` Willy Tarreau 2021-02-18 17:19 ` Jari Ruusu 2021-02-18 17:19 ` Jari Ruusu 2021-02-18 17:22 ` Russell King - ARM Linux admin 2021-02-18 17:22 ` Russell King - ARM Linux admin 2021-02-18 17:44 ` Greg Kroah-Hartman 2021-02-18 17:44 ` Greg Kroah-Hartman 2021-02-19 7:10 ` Jari Ruusu 2021-02-19 7:10 ` Jari Ruusu 2021-02-19 8:22 ` Greg Kroah-Hartman 2021-02-19 8:22 ` Greg Kroah-Hartman 2021-02-19 10:31 ` Jari Ruusu 2021-02-19 10:31 ` Jari Ruusu 2021-02-19 10:37 ` Greg Kroah-Hartman 2021-02-19 10:37 ` Greg Kroah-Hartman 2021-02-19 10:57 ` Jari Ruusu 2021-02-19 10:57 ` Jari Ruusu 2021-02-19 11:16 ` Greg Kroah-Hartman 2021-02-19 11:16 ` Greg Kroah-Hartman 2021-02-19 15:23 ` Jari Ruusu 2021-02-19 15:23 ` Jari Ruusu 2021-02-20 13:29 ` Jari Ruusu 2021-02-20 13:29 ` Jari Ruusu 2021-02-20 16:05 ` Greg Kroah-Hartman 2021-02-20 16:05 ` Greg Kroah-Hartman 2021-02-20 17:06 ` Willy Tarreau 2021-02-20 17:06 ` Willy Tarreau 2021-02-21 11:38 ` Jari Ruusu 2021-02-21 11:38 ` Jari Ruusu 2021-02-19 16:50 ` Theodore Ts'o 2021-02-19 16:50 ` Theodore Ts'o 2021-02-18 17:16 ` Florian Fainelli 2021-02-18 17:16 ` Florian Fainelli 2021-02-18 12:51 ` Pavel Machek 2021-02-18 12:51 ` Pavel Machek 2021-02-18 16:51 ` Sasha Levin 2021-02-18 16:51 ` Sasha Levin 2021-02-18 17:21 ` Florian Fainelli 2021-02-18 17:21 ` Florian Fainelli 2021-02-18 17:53 ` Greg Kroah-Hartman 2021-02-18 17:53 ` Greg Kroah-Hartman 2021-02-18 17:57 ` Florian Fainelli 2021-02-18 17:57 ` Florian Fainelli 2021-02-18 18:20 ` Willy Tarreau 2021-02-18 18:20 ` Willy Tarreau 2021-02-18 18:36 ` Greg Kroah-Hartman 2021-02-18 18:36 ` Greg Kroah-Hartman 2021-02-18 20:16 ` Scott Branden 2021-02-18 20:16 ` Scott Branden 2021-02-18 21:00 ` Willy Tarreau 2021-02-18 21:00 ` Willy Tarreau 2021-02-18 22:38 ` Scott Branden 2021-02-18 22:38 ` Scott Branden 2021-02-18 21:39 ` Sasha Levin 2021-02-18 21:39 ` Sasha Levin 2021-02-18 22:00 ` Florian Fainelli 2021-02-18 22:00 ` Florian Fainelli 2021-02-18 22:26 ` Scott Branden 2021-02-18 22:26 ` Scott Branden 2021-02-19 8:25 ` Greg Kroah-Hartman 2021-02-19 8:25 ` Greg Kroah-Hartman 2021-02-19 15:05 ` Florian Fainelli 2021-02-19 15:05 ` Florian Fainelli 2021-02-19 15:53 ` Greg Kroah-Hartman 2021-02-19 15:53 ` Greg Kroah-Hartman 2021-02-19 17:44 ` Florian Fainelli 2021-02-19 17:44 ` Florian Fainelli 2021-02-22 14:17 ` Greg Kroah-Hartman 2021-02-22 14:17 ` Greg Kroah-Hartman 2021-02-18 17:42 ` Florian Fainelli 2021-02-18 17:42 ` Florian Fainelli 2021-02-18 18:13 ` Willy Tarreau 2021-02-18 18:13 ` Willy Tarreau 2021-02-18 10:04 ` Pavel Machek 2021-02-18 10:04 ` Pavel Machek 2021-01-29 9:49 ` Pavel Machek 2021-02-19 8:54 ` Hanjun Guo 2021-02-19 8:54 ` Hanjun Guo 2021-02-19 9:08 ` Greg Kroah-Hartman 2021-02-19 9:08 ` Greg Kroah-Hartman 2021-02-20 7:02 ` Hanjun Guo 2021-02-20 7:02 ` Hanjun Guo 2021-02-20 9:53 ` Greg Kroah-Hartman 2021-02-20 9:53 ` Greg Kroah-Hartman 2021-02-23 2:14 ` Hanjun Guo 2021-02-23 2:14 ` Hanjun Guo 2021-02-19 14:45 ` Nikolai Kondrashov 2021-02-19 14:45 ` Nikolai Kondrashov 2021-02-26 8:03 ` Hanjun Guo 2021-02-26 8:03 ` Hanjun Guo 2021-02-26 8:03 ` Hanjun Guo 2021-02-26 11:21 ` Nikolai Kondrashov [this message] 2021-02-26 11:21 ` Nikolai Kondrashov 2021-02-22 14:00 ` Nishanth Aravamudan 2021-02-22 14:00 ` Nishanth Aravamudan 2021-02-22 14:24 ` Greg Kroah-Hartman 2021-02-22 14:24 ` Greg Kroah-Hartman
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=a8518d24-8b02-39f7-d4e3-82c28715191d@redhat.com \ --to=nikolai.kondrashov@redhat.com \ --cc=PEIXIN.HOU@huawei.com \ --cc=bcm-kernel-feedback-list@broadcom.com \ --cc=gregkh@linuxfoundation.org \ --cc=guohanjun@huawei.com \ --cc=huxinwei@huawei.com \ --cc=kernelci@groups.io \ --cc=lijinyue@huawei.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=scott.branden@broadcom.com \ --cc=weiyongjun1@huawei.com \ --cc=yanjin.yan@huawei.com \ --cc=zhangdianfang@huawei.com \ --cc=zhaohongjiang@huawei.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: linkBe 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.