mirror of https://github.com/aya-rs/aya
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.
d1457acc6d
We're seeing 429 from Github trying to download gen_init_cpio, so cache it using actions cache. Since I'm here add this for kernel images as well to save time waiting on slow Debian servers. |
4 weeks ago | |
---|---|---|
.. | ||
integration-common | 2 months ago | |
integration-ebpf | 2 months ago | |
integration-test | 2 months ago | |
.gitignore | 3 years ago | |
README.md | 4 weeks 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:
rustup toolchain install nightly
rustup target add {aarch64,x86_64}-unknown-linux-musl
cargo install bpf-linker
libelf-dev
(libelf-devel
on rpm-based distros)llvm
(forllvm-objcopy
)- (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 inintegration-ebpf/Cargo.toml
andintegration-test/src/lib.rs
usinginclude_bytes_aligned!
. - C eBPF code should live in
integration-test/bpf/${NAME}.bpf.c
. It should be added to the list of files inintegration-test/build.rs
and the list of constants inintegration-test/src/lib.rs
usinginclude_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 topanic!
instead.