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.

History

Andrew Werner 97eb8afeac integration-test: use nightly toolchain with ebpf The ebpf probes require a nightly compiler. Before this change, if you ran `cargo xtask integration-test` with a stable compiler toolchain as default, or you ran `cargo +stable xtask integration-test`, you would have seen an error like the one below. This is now fixed by running the cargo build command in the integration-ebpf directory and making sure to clear the RUSTUP_TOOLCHAIN env var. ``` --- stderr /home/ajwerner/src/github.com/aya-rs/aya/test/integration-test/bpf/ring_buf_sched_tracepoint.bpf.c:18:21: warning: declaration of 'struct switch_args' will not be visible outside of this function [-Wvisibility] int bpf_prog(struct switch_args* ctx) ^ 1 warning generated. error: the `-Z` flag is only accepted on the nightly channel of Cargo, but this is the `stable` channel See https://doc.rust-lang.org/book/appendix-07-nightly-rust.html for more information about Rust release channels. thread 'main' panicked at '"cargo" "build" "-p" "integration-ebpf" "-Z" "build-std=core" "--release" "--message-format=json" "--target" "bpfel-unknown-none" "--target-dir" "/home/ajwerner/src/github.com/aya-rs/aya/target/debug/build/integration-test-9bbcb3db5e9f8f57/out/integration-ebpf" exited with status code 101: ', test/integration-test/build.rs:219:25 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace Error: error while building userspace application Caused by: Child { stdin: None, stdout: None, stderr: None, .. } exited with status code 101: ```		1 year ago
..
integration-ebpf	integration-test: use nightly toolchain with ebpf	1 year ago
integration-test	integration-test: use nightly toolchain with ebpf	1 year ago
.gitignore	test: Replace RTF with Rust	2 years ago
README.md	test: update README.md	1 year ago
cloud-localds	integration-tests: run on macos to get nested virtualization	2 years ago
run.sh	xtask: ensure libbpf submodule is initialized	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:

Rust nightly
cargo install bpf-linker
bpftool ¹

Other OSs

A POSIX shell
rustup target add x86_64-unknown-linux-musl
cargo install bpf-linker
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.

TODO(https://github.com/aya-rs/aya/issues/645): Remove this dependency. ↩︎