You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
aya/test
Ershaad Basheer d8bd45b84c fix consumer index handling for pinned ringbuf map
Newly loaded ring buffer maps assumed that the consumer index was at
position 0. This is not always true for pinned maps since they are
persistent and therefore remember the consumer index position from the
last time that they were read from

Fixes: #1309
1 month ago
..
integration-common taplo: reorder-keys 6 months ago
integration-ebpf fix consumer index handling for pinned ringbuf map 1 month ago
integration-test fix consumer index handling for pinned ringbuf map 1 month ago
.gitignore test: Replace RTF with Rust 3 years ago
README.md ci: cache downloads 9 months ago

README.md

Aya Integration Tests

The aya integration test suite is a set of tests to ensure that common usage behaviours work on real Linux distros

Prerequisites

You'll need:

  1. rustup toolchain install nightly
  2. rustup target add {aarch64,x86_64}-unknown-linux-musl
  3. cargo install bpf-linker
  4. libelf-dev (libelf-devel on rpm-based distros)
  5. llvm (for llvm-objcopy)
  6. (virtualized only) qemu

Usage

From the root of this repository:

Native

cargo xtask integration-test local

Virtualized

cargo xtask integration-test vm --cache-dir <CACHE_DIR> <KERNEL_IMAGE>...

Writing an integration test

Tests should follow these guidelines:

  • Rust eBPF code should live in integration-ebpf/${NAME}.rs and included in integration-ebpf/Cargo.toml and integration-test/src/lib.rs using include_bytes_aligned!.
  • C eBPF code should live in integration-test/bpf/${NAME}.bpf.c. It should be added to the list of files in integration-test/build.rs and the list of constants in integration-test/src/lib.rs using include_bytes_aligned!.
  • Tests should be added to integration-test/tests.
  • You may add a new module, or use an existing one.
  • Test functions should not return anyhow::Result<()> since this produces errors without stack traces. Prefer to panic! instead.