All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manu Bretelle <chantr4@gmail.com>
To: lsf-pc@lists.linux-foundation.org
Cc: bpf@vger.kernel.org
Subject: [LSF/MM/BPF TOPIC] BPF CI: A year later
Date: Thu, 2 Mar 2023 09:32:00 -0800	[thread overview]
Message-ID: <ZADdkKaGcEmjC0tF@worktop> (raw)

Last year, Mykola Lysenko presented how BPF CI [0] works ([1][2]). This year we
would like to go over what has happened behind the BPF CI system curtains, what
improvements were made, what issues were encountered, and which pain points we
are still battling with.

We would also like to take the opportunity to close the talk with an interactive
demo for the audience to run a change that goes through the BPF CI [3] so people
can benefit from a multi-arch environment to validate their changes before
submitting it to the mailing list.

Finally, we would like to hear feedback from the audience to better understand
what are contributors challenges with regards to testing, as well as probably
find overlapping areas (vmtest [4] anyone?) where we could benefit from better
cooperation.

Thanks,

Manu

[0] https://github.com/kernel-patches/bpf
[1] https://youtu.be/CkM_HZ--vkI
[2] https://docs.google.com/presentation/d/1RQZjLkbXmSFOr_4Sj5BdQsXbUh_vMshXi7w09pUpWsY/edit#slide=id.p
[3] https://www.kernel.org/doc/html/latest/bpf/bpf_devel_QA.html#q-how-do-i-run-bpf-ci-on-my-changes-before-sending-them-out-for-review
[4] https://lore.kernel.org/bpf/f1ea109c-5f07-4734-83f5-12c4252fa5ae@app.fastmail.com/T/#t

                 reply	other threads:[~2023-03-02 17:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=ZADdkKaGcEmjC0tF@worktop \
    --to=chantr4@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.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.