All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Andrii Nakryiko <andriin@fb.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, ast@fb.com,
	daniel@iogearbox.net, andrii.nakryiko@gmail.com,
	kernel-team@fb.com
Subject: Re: [PATCH v3 bpf-next] selftests/bpf: merge most of test_btf into test_progs
Date: Tue, 15 Sep 2020 18:39:33 -0700	[thread overview]
Message-ID: <20200916013933.lflk4peklgl2hi7q@ast-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <20200916004819.3767489-1-andriin@fb.com>

On Tue, Sep 15, 2020 at 05:48:19PM -0700, Andrii Nakryiko wrote:
> Merge 183 tests from test_btf into test_progs framework to be exercised
> regularly. All the test_btf tests that were moved are modeled as proper
> sub-tests in test_progs framework for ease of debugging and reporting.
> 
> No functional or behavioral changes were intended, I tried to preserve
> original behavior as much as possible. E.g., `test_progs -v` will activate
> "always_log" flag to emit BTF validation log.
> 
> The only difference is in reducing the max_entries limit for pretty-printing
> tests from (128 * 1024) to just 128 to reduce tests running time without
> reducing the coverage.
> 
> Example test run:
> 
>   $ sudo ./test_progs -n 8
>   ...
>   #8 btf:OK
>   Summary: 1/183 PASSED, 0 SKIPPED, 0 FAILED
> 
> Signed-off-by: Andrii Nakryiko <andriin@fb.com>

Applied. Thanks.

Now we have that rcu warn in bpf-next tree. I'll send bpf PR shortly to
converge the trees.

      reply	other threads:[~2020-09-16  1:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-16  0:48 [PATCH v3 bpf-next] selftests/bpf: merge most of test_btf into test_progs Andrii Nakryiko
2020-09-16  1:39 ` Alexei Starovoitov [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=20200916013933.lflk4peklgl2hi7q@ast-mbp.dhcp.thefacebook.com \
    --to=alexei.starovoitov@gmail.com \
    --cc=andrii.nakryiko@gmail.com \
    --cc=andriin@fb.com \
    --cc=ast@fb.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kernel-team@fb.com \
    --cc=netdev@vger.kernel.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.