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 e276c07f73 integration-ebpf: invalidate on bpf-linker Extract the symlink-to-bpf-linker logic from integration-test to xtask and use it in a new build script in integration-ebpf, causing ebpf probes to be rebuilt when bpf-linker changes. Previously bpf-linker changes would rebuild integration-test, but not integration-ebpf, resulting in stale tests. Note that this still doesn't address the possibility that a new bpf-linker is added to the PATH ahead of the cached one. Solving this in the general case would require rebuild-if-changed-env=PATH and rebuild-if-changed={every-directory-in-PATH} which would likely mean far too much cache invalidation.		2 years ago
..
integration-ebpf	integration-ebpf: invalidate on bpf-linker	2 years ago
integration-test	integration-ebpf: invalidate on bpf-linker	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	3 years ago
run.sh	xtask: ensure libbpf submodule is initialized	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.