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
Michal Rostecki 6685ae7aa2 ci: Use pre-release LLVM versions from tarballs
Instead of relying on Homebrew for macOS (which ships older LLVM
versions) and `apt.llvm.org` for Linux (which often has bugs at the
packaging level), we now use:

- The tarball from Rust CI to provide `libLLVM`. This ensures it always
  matches the version used by the latest Rust nightly.
- The tarball from https://github.com/llvm/llvm-project to provide
  `clang` and `llvm-objcopy`. In this case, an exact match with
  `libLLVM` in `rustc` is not necessary. Nevertheless, using the latest
  versions is preferred.

Fixing the build on macOS runners is the main motivation behind this
change.

Co-authored-by: tyrone-wu <wudevelops@gmail.com>
3 days ago
..
integration-ebpf ci: Use pre-release LLVM versions from tarballs 3 days ago
integration-test ci: Use pre-release LLVM versions from tarballs 3 days ago
.gitignore test: Replace RTF with Rust 2 years ago
README.md tests: update instructions on setting up and running tests 10 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:

  1. rustup toolchain install nightly
  2. rustup target add {aarch64,x86_64}-unknown-linux-musl
  3. cargo install bpf-linker
  4. libelf-dev (libelf-devel on rpm-based distros)
  5. llvm (for llvm-objcopy)
  6. (virtualized only) qemu

Usage

From the root of this repository:

Native

cargo xtask integration-test local

Virtualized

cargo xtask integration-test vm <KERNEL IMAGE>

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.