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

Addison Crump 55aa5a655d Prevent verification failure by making the log level static immutable The log level implementation in #1335 was incomplete as the verifier could reject programs which exceeded their instruction limits within logging statements. This commit addresses this issue by making the log level static variable immutable (s.t. the compiler puts it in a read-only section) and adds an additional test which the verifier will reject as an infinite loop iff it is unable to detect that the static variable would otherwise allow the logging.		7 days ago
..
integration-common	taplo: reorder-keys	6 months ago
integration-ebpf	Prevent verification failure by making the log level static immutable	7 days ago
integration-test	Prevent verification failure by making the log level static immutable	7 days ago
.gitignore	test: Replace RTF with Rust	3 years ago
README.md	ci: cache downloads	9 months 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 --cache-dir <CACHE_DIR> <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.