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

Andre Fredette f5d4fdedba Exercise all new TCX APIs in the TCX integration test Also removed unused code in the tcx eBPF program. I've manually verified that all the programs get attached in the correct order. TODO: Add code to the integration test to automatically verify that the programs are attached in the correct order after the API based on the BPF_PROG_QUERY syscall has been implemented. Signed-off-by: Andre Fredette <afredette@redhat.com>		7 months ago
..
integration-ebpf	Exercise all new TCX APIs in the TCX integration test	7 months ago
integration-test	Exercise all new TCX APIs in the TCX integration test	7 months ago
.gitignore	test: Replace RTF with Rust	3 years ago
README.md	tests: update instructions on setting up and running tests	1 year ago

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:

From the root of this repository:

cargo xtask integration-test local

cargo xtask integration-test vm <KERNEL IMAGE>

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.