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

Dave Tucker bf7fdff1ce aya: Find programs using the symbol table This makes a few changes to the way that Aya reads the ELF object files. 1. To find programs in a section, we use the symbols table. This allows for cases where multiple programs could appear in the same section. 2. When parsing our ELF file we build symbols_by_section_index as an optimization as we use it for legacy maps, BTF maps and now programs. As a result of theses changes the "NAME" used in `bpf.prog_mut("NAME")` is now ALWAYS the same as the function name in the eBPF code, making the user experience more consistent. Signed-off-by: Dave Tucker <dave@dtucker.co.uk>		2 years ago
..
integration-ebpf	aya: Find programs using the symbol table	2 years ago
integration-test	aya: Find programs using the symbol table	2 years ago
.gitignore	test: Replace RTF with Rust	3 years ago
README.md	test: update README.md	2 years ago
cloud-localds	integration-tests: run on macos to get nested virtualization	2 years ago
run.sh	integration-tests: run in release also	2 years ago

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

To run locally all you need is:

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

From the root of this repository:

cargo xtask integration-test

./test/run.sh

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.