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 3cfd886dc5 log: annotate logging functions inlining Some of these functions fail to compile when not inlined, so we should be explicit. Before deciding on this approach I tried various ways of making all these functions #[inline(never)] to save instructions but I ran into blockers: - These functions currently return Result, which is a structure. This is not permitted in BPF. - I tried inventing a newtype that is a #[repr(transparent)] wrapper of u16, and having these functions return that; however it seems that even if the object code is legal, the verifier will reject such functions because the BTF (if present, and it was in my local experiments) would indicate that the return is a structure. - I tried having these functions return a plain u16 where 0 means error, but the verifier still rejected the BTF because the receiver (even if made into &self) is considered a structure, and forbidden. We can eventually overcome these problems by "lying" in our BTF once support for it matures in the bpf-linker repo (e.g. Option<NonZeroU16> should be perfectly legal as it is guaranteed to be word-sized), but we aren't there yet, and this is the safest thing we can do for now.		1 year ago
..
integration-ebpf	log: annotate logging functions inlining	1 year ago
integration-test	log: annotate logging functions inlining	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.