From: Greg KH <gregkh@linuxfoundation.org>
To: Veronika Kabatova <vkabatov@redhat.com>
Cc: automated-testing@yoctoproject.org, info@kernelci.org,
Tim.Bird@sony.com, khilamn@baylibre.org,
syzkaller@googlegroups.com, lkp@lists.01.org,
stable@vger.kernel.org, Laura Abbott <labbott@redhat.com>,
Eliska Slobodova <eslobodo@redhat.com>,
CKI Project <cki-project@redhat.com>
Subject: Re: CKI hackfest @Plumbers invite
Date: Tue, 21 May 2019 18:47:04 +0200 [thread overview]
Message-ID: <20190521164704.GB8787@kroah.com> (raw)
In-Reply-To: <1667759567.21267950.1558450452057.JavaMail.zimbra@redhat.com>
On Tue, May 21, 2019 at 10:54:12AM -0400, Veronika Kabatova wrote:
> Hi,
>
> as some of you have heard, CKI Project is planning hackfest CI meetings after
> Plumbers conference this year (Sept. 12-13). We would like to invite everyone
> who has interest in CI for kernel to come and join us.
>
> The early agenda with summary is at the end of the email. If you think there's
> something important missing let us know! Also let us know in case you'd want to
> lead any of the sessions, we'd be happy to delegate out some work :)
>
>
> Please send us an email as soon as you decide to come and feel free to invite
> other people who should be present. We are not planning to cap the attendance
> right now but need to solve the logistics based on the interest. The event is
> free to attend, no additional registration except letting us know is needed.
>
> Feel free to contact us if you have any questions,
> Veronika
> CKI Project
>
>
> -----------------------------------------------------------
> Here is an early agenda we put together:
> - Introductions
> - Common place for upstream results, result publishing in general
> - The discussion on the mailing list is going strong so we might be able to
> substitute this session for a different one in case everything is solved by
> September.
> - Test result interpretation and bug detection
> - How to autodetect infrastructure failures, regressions/new bugs and test
> bugs? How to handle continuous failures due to known bugs in both tests and
> kernel? What's your solution? Can people always trust the results they
> receive?
> - Getting results to developers/maintainers
> - Aimed at kernel developers and maintainers, share your feedback and
> expectations.
> - How much data should be sent in the initial communication vs. a click away
> in a dashboard? Do you want incremental emails with new results as they come
> in?
> - What about adding checks to tested patches in Patchwork when patch series
> are being tested?
> - Providing enough data/script to reproduce the failure. What if special HW
> is needed?
> - Onboarding new kernel trees to test
> - Aimed at kernel developers and maintainers.
> - Which trees are most prone to bring in new problems? Which are the most
> critical ones? Do you want them to be tested? Which tests do you feel are
> most beneficial for specific trees or in general?
> - Security when testing untrusted patches
> - How do we merge, compile, and test patches that have untrusted code in them
> and have not yet been reviewed? How do we avoid abuse of systems,
> information theft, or other damage?
> - Check out the original patch that sparked the discussion at
> https://patchwork.ozlabs.org/patch/862123/
> - Avoiding effort duplication
> - Food for thought by GregKH
So I guess I'm going to be there?
Ok, fair enough, I'll be present, looks good :)
thanks,
greg k-h
next prev parent reply other threads:[~2019-05-21 16:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1204558561.21265703.1558449611621.JavaMail.zimbra@redhat.com>
2019-05-21 14:54 ` CKI hackfest @Plumbers invite Veronika Kabatova
2019-05-21 16:47 ` Greg KH [this message]
2019-05-22 10:14 ` Veronika Kabatova
2019-05-24 20:17 ` Tim.Bird
2019-05-27 11:52 ` Veronika Kabatova
2019-05-27 14:39 ` Dmitry Vyukov
2019-05-27 15:42 ` Veronika Kabatova
2019-06-05 20:46 ` Dan Rue
2019-06-05 22:00 ` Shuah Khan
2019-06-06 10:00 ` Veronika Kabatova
2019-06-07 16:27 ` Dmitry Vyukov
2019-06-21 23:01 ` Shuah Khan
2019-06-06 6:30 ` Tomeu Vizoso
2019-06-06 10:42 ` [Automated-testing] " Michal Simek
2019-06-06 11:08 ` Mark Brown
[not found] ` <CAH1_8nAx-1+uqOwAOCfGbqdWzgWD1-oikAfoVBqw4qPcu8v4fw@mail.gmail.com>
2019-06-20 16:11 ` Veronika Kabatova
2019-06-24 18:55 ` Tim.Bird
2019-06-26 11:57 ` Veronika Kabatova
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=20190521164704.GB8787@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Tim.Bird@sony.com \
--cc=automated-testing@yoctoproject.org \
--cc=cki-project@redhat.com \
--cc=eslobodo@redhat.com \
--cc=info@kernelci.org \
--cc=khilamn@baylibre.org \
--cc=labbott@redhat.com \
--cc=lkp@lists.01.org \
--cc=stable@vger.kernel.org \
--cc=syzkaller@googlegroups.com \
--cc=vkabatov@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).