yanguangshaonian
/
aya
mirror of https://github.com/aya-rs/aya
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
aya/test
History
Andrew Stoycos 94f554a52f
fix loaded_programs() race in int-tests 
in the integration tests we recenctly switched to using
our internal api to list programs. I was seeing times when
this would race and panic internally (program fd was deleted
by aya WHILE we were trying to get it).  This ensures that
the list succeeded without panicking.

Signed-off-by: Andrew Stoycos <astoycos@redhat.com>
..
integration-ebpf Add integration test for perf link pin
integration-test fix loaded_programs() race in int-tests
.gitignore test: Replace RTF with Rust
README.md integration-test: compile Rust probes using build.rs
cloud-localds integration-tests: run on macos to get nested virtualization
run.sh re-add bpftool to integration tests

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:

  1. Rust nightly
  2. libelf
  3. A checkout of libbpf
  4. cargo install bpf-linker
  5. bpftool

Other OSs

  1. A POSIX shell
  2. A checkout of libbpf
  3. rustup target add x86_64-unknown-linux-musl
  4. cargo install bpf-linker
  5. 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

./test/run.sh

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.