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.
aya/test
Tamir Duberstein 8c61fc9ea6
integration-test: compile C probes using build.rs
- Add libbpf as a submodule. This prevents having to plumb its location
  around (which can't be passed to Cargo build scripts) and also
  controls the version against which codegen has run.
- Move bpf written in C to the integration-test crate and define
  constants for each probe.
- Remove magic; each C source file must be directly enumerated in the
  build script and in lib.rs.
1 year ago
..
integration-ebpf integration-test: compile C probes using build.rs 1 year ago
integration-test integration-test: compile C probes using build.rs 1 year ago
.gitignore test: Replace RTF with Rust 2 years ago
README.md integration-test: compile C probes using build.rs 1 year ago
cloud-localds integration-tests: run on macos to get nested virtualization 2 years ago
run.sh integration-test: compile C probes using build.rs 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:

  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.
  • 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.