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.

History

Tamir Duberstein b46fb616be integration-test: fix BTF relocation test The struct_flavors test previously expected the same thing with and without relocations. It now expects different values. Also rename an enum variant "u64" to "S64". This was a typo. Turns out that U32 is a type that exists in kernel headers, so all enum values are suffixed with "_VAL". Remove stdlib.h and the call to exit(). This alone makes the test fail with a poisoned relocation. Bringing over the map definition makes the test work again.		1 year ago
..
integration-ebpf	integration-test: Add test for 2 progs in same section	1 year ago
integration-test	integration-test: fix BTF relocation test	1 year ago
.gitignore	test: Replace RTF with Rust	2 years ago
README.md	Add links iterator	1 year ago
cloud-localds	integration-tests: run on macos to get nested virtualization	2 years ago
run.sh	Add links iterator	1 year 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

Linux

To run locally all you need is:

Rust nightly
cargo install bpf-linker

Other OSs

A POSIX shell
rustup target add x86_64-unknown-linux-musl
cargo install bpf-linker
Install qemu and cloud-init-utils package - or any package that provides cloud-localds

Usage

From the root of this repository:

Native

cargo xtask integration-test

Virtualized

mkdir -p integration-test-binaries
cargo xtask build-integration-test | xargs -I % cp % integration-test-binaries
./test/run.sh integration-test-binaries

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.