mirror of https://github.com/aya-rs/aya
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.
de7972483b
Before this change:
```
error[E0382]: use of moved value: `no_copy`
--> test/integration-ebpf/src/log.rs:35:9
|
33 | let no_copy = NoCopy {};
| ------- move occurs because `no_copy` has type `NoCopy`, which does not implement the `Copy` trait
34 |
35 | debug!(&ctx, "{:x}", no_copy.consume());
| ^^^^^^^^^^^^^^^^^^^^^-------^---------^
| | | |
| | | `no_copy` moved due to this method call
| | use occurs due to use in closure
| value used here after move
|
note: `NoCopy::consume` takes ownership of the receiver `self`, which moves `no_copy`
--> test/integration-ebpf/src/log.rs:28:24
|
28 | fn consume(self) -> u64 {
| ^^^^
= note: this error originates in the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
For more information about this error, try `rustc --explain E0382`.
error: could not compile `integration-ebpf` (bin "log") due to previous error
```
|
1 year ago | |
|---|---|---|
| .. | ||
| integration-ebpf | 1 year ago | |
| integration-test | 1 year ago | |
| integration-test-macros | 2 years ago | |
| .gitignore | 2 years ago | |
| README.md | 2 years ago | |
| cloud-localds | 2 years ago | |
| run.sh | 2 years 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
libelf- A checkout of libbpf
cargo install bpf-linkerbpftool
Other OSs
- A POSIX shell
- A checkout of libbpf
rustup target add x86_64-unknown-linux-muslcargo install bpf-linker- Install
qemuandcloud-init-utilspackage - or any package that providescloud-localds
Usage
From the root of this repository:
Native
cargo xtask integration-test --libbpf-dir /path/to/libbpf
Virtualized
./test/run.sh /path/to/libbpf
Writing a test
Tests should follow these guidelines:
- Rust eBPF code should live in
integration-ebpf/${NAME}.rsand included inintegration-ebpf/Cargo.toml - C eBPF code should live in
integration-test/src/bpf/${NAME}.bpf.c. It's automatically compiled and made available as${OUT_DIR}/${NAME}.bpf.o. - Any bytecode should be included in the integration test binary using
include_bytes_aligned! - Tests should be added to
integration-test/src/test - You may add a new module, or use an existing one
- Integration tests must use the
#[integration_test]macro to be included in the build - Test functions should return
anyhow::Result<()>since this allows the use of?to return errors. - You may either
panic!when an assertion fails orbail!. The former is preferred since the stack trace will point directly to the failed line.