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.
f0a9f19ddc
Change FromRawTracepointArgs::arg to return T rather than *const T which seems to have been returning a dangling pointer. Arguably this is not strictly necessary; edition 2024 seems to be focused on increased strictness around unsafe code which doesn't unlock new functionality for our users. That said, this work revealed an apparent bug (see above) that we wouldn't otherwise catch due to allow-by-default lints. |
1 week ago | |
|---|---|---|
| .. | ||
| integration-common | 1 week ago | |
| integration-ebpf | 1 week ago | |
| integration-test | 1 week ago | |
| .gitignore | 3 years ago | |
| README.md | 3 months 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 nightlyrustup target add {aarch64,x86_64}-unknown-linux-muslcargo install bpf-linkerlibelf-dev(libelf-develon 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}.rsand included inintegration-ebpf/Cargo.tomlandintegration-test/src/lib.rsusinginclude_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.rsand the list of constants inintegration-test/src/lib.rsusinginclude_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.