public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Jiri Benc <jbenc@redhat•com>
To: Andrii Nakryiko <andrii.nakryiko@gmail•com>
Cc: Andrii Nakryiko <andriin@fb•com>, bpf <bpf@vger•kernel.org>,
	Networking <netdev@vger•kernel.org>,
	Alexei Starovoitov <ast@fb•com>,
	Daniel Borkmann <daniel@iogearbox•net>,
	Kernel Team <kernel-team@fb•com>
Subject: Re: [PATCH v3 bpf-next] bpf: make verifier log more relevant by default
Date: Fri, 6 Nov 2020 09:26:24 +0100	[thread overview]
Message-ID: <20201106092624.5b0487e1@redhat.com> (raw)
In-Reply-To: <CAEf4Bzb7r-9TEAnQC3gwiwX52JJJuoRd_ZHrkGviiuFKvy8qJg@mail.gmail.com>

On Thu, 5 Nov 2020 13:22:12 -0800, Andrii Nakryiko wrote:
> test_progs is the only test runner that's run continuously on every
> patch. libbpf CI also runs test_maps and test_verifier. All the other
> test binaries/scripts rely on humans to not forget about them. Which
> works so-so, as you can see :)

Did not know that, thanks for the explanation.

Would be good to add full testing to some of the numerous CIs we have
(some taker? :-)).

 Jiri


      parent reply	other threads:[~2020-11-06  8:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-23 19:58 [PATCH v3 bpf-next] bpf: make verifier log more relevant by default Andrii Nakryiko
2020-04-26 16:57 ` Alexei Starovoitov
2020-04-28  4:55   ` Andrii Nakryiko
2020-11-05 16:02 ` Jiri Benc
2020-11-05 21:22   ` Andrii Nakryiko
2020-11-05 21:53     ` Jakub Kicinski
2020-11-05 22:41       ` Andrii Nakryiko
2020-11-05 22:57         ` Jakub Kicinski
2020-11-06  8:24           ` Jiri Benc
2020-11-06 18:52             ` Jakub Kicinski
2020-11-06  8:26     ` Jiri Benc [this message]

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=20201106092624.5b0487e1@redhat.com \
    --to=jbenc@redhat$(echo .)com \
    --cc=andrii.nakryiko@gmail$(echo .)com \
    --cc=andriin@fb$(echo .)com \
    --cc=ast@fb$(echo .)com \
    --cc=bpf@vger$(echo .)kernel.org \
    --cc=daniel@iogearbox$(echo .)net \
    --cc=kernel-team@fb$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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