eb25a51b36
The logic about testing API levels was wrong: it simply isn't
meaningful to say it doesn't support and needs to be updated for U+.
This test *always* needs to be kept up to date wrt. any changes
we make to mainline provided bpf programs and maps.
That's why the test is in the same git repo and is MTS not CTS.
Additionally we *can* make (and have made) changes to programs/maps
available on older API levels as well, so it's not even set in stone
for older API levels either.
Getting rid of the api level checks simplifies things.
As does moving the 4.9+ check into the test logic itself.
This has the added benefit of not skipping the test on S
simply because kernel is < 4.9 [not that's valid, but...].
Test: TreeHugger
Signed-off-by: Maciej Żenczykowski <maze@google.com>
Change-Id: Ib0400f4534254b7a35a96d364720a7c800953456
Former-commit-id:
|
||
---|---|---|
.. | ||
Android.bp | ||
bpf_existence_test.cpp |