yanguangshaonian
/
aya
mirror of https://github.com/aya-rs/aya
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
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.
main
pr/Billy99/974
linker-bindep
fix-verifier-blixt
revert-461-main
gh-pages
ci
perf-event
aya-v0.13.1
aya-obj-v0.2.1
aya-log-v0.2.1
aya-log-common-v0.1.15
aya-ebpf-bindings-v0.1.1
aya-ebpf-cty-v0.2.2
aya-v0.13.0
aya-obj-v0.2.0
aya-log-ebpf-v0.1.0
aya-log-ebpf-macros-v0.1.0
aya-log-parser-v0.1.13
aya-ebpf-v0.1.0
aya-ebpf-macros-v0.1.0
aya-ebpf-bindings-v0.1.0
aya-ebpf-cty-v0.2.1
aya-log-v0.2.0
aya-log-common-v0.1.14
aya-v0.12.0
aya-obj-v0.1.0
aya-log-common-v0.1.13
aya-log-v0.1.13
aya-log-common-v0.1.11
aya-log-v0.1.11
aya-log-common-v0.1.10
aya-log-v0.1.10
aya-v0.11.0
aya-log-common-v0.1.9
aya-log-v0.1.9
aya-v0.10.7
aya-v0.10.6
aya-log-v0.1.1
aya-v0.10.5
aya-v0.10.4
aya-v0.10.3
aya-v0.10.2
aya-v0.10.1
aya-v0.10.0
aya-ebpf-macros-v0.1.1
aya-ebpf-v0.1.1
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '13b1fc63ef'
${ noResults }
aya/test/integration-test/Cargo.toml

47 lines
2.0 KiB
TOML
Raw Normal View History Unescape Escape

test: Replace RTF with Rust This commit replaces the existing RTF test runner with a simple rust binary package called - integration-test. integration-test depends on integration-ebpf, which contains test eBPF code written in Rust and C. `cargo xtask build-integration-test-ebpf` can be used to build this code and supress rust-analyzer warnings. It does require `bpf-linker`, but that is highly likely to be available to developers of Aya. It also requires a checkout of `libbpf` to extract headers like bpf-helpers.h. Since everything is compiled into a single binary, it can be run be run locally using `cargo xtask integration-test` or remotely using `./run.sh` which re-uses the bash script from the old test framework to spawn a VM in which to run the tests. Signed-off-by: Dave Tucker <dave@dtucker.co.uk>
2 years ago
[package]
name = "integration-test"
version = "0.1.0"
publish = false
chore: Use the cargo workspace package table This allows for inheritance of common fields from the workspace root. The following fields have been made common: - authors - license - repository - homepage - edition Signed-off-by: Dave Tucker <dave@dtucker.co.uk>
9 months ago
authors.workspace = true
license.workspace = true
repository.workspace = true
homepage.workspace = true
edition.workspace = true
test: Replace RTF with Rust This commit replaces the existing RTF test runner with a simple rust binary package called - integration-test. integration-test depends on integration-ebpf, which contains test eBPF code written in Rust and C. `cargo xtask build-integration-test-ebpf` can be used to build this code and supress rust-analyzer warnings. It does require `bpf-linker`, but that is highly likely to be available to developers of Aya. It also requires a checkout of `libbpf` to extract headers like bpf-helpers.h. Since everything is compiled into a single binary, it can be run be run locally using `cargo xtask integration-test` or remotely using `./run.sh` which re-uses the bash script from the old test framework to spawn a VM in which to run the tests. Signed-off-by: Dave Tucker <dave@dtucker.co.uk>
2 years ago
[dependencies]
Cargo.toml: Remove default-features settings These are all set to false at the root.
1 year ago
anyhow = { workspace = true, features = ["std"] }
cargo: Define dependencies on the workspace level This way we will avoid version mismatches and make differences in features across our crates clearer.
1 year ago
assert_matches = { workspace = true }
chore: Don't use path deps in workspace This moves the path dependencies back into the per-crate Cargo.toml. It is required such that the release tooling can correctly calculate which version constraints require changing when we perform a release. Signed-off-by: Dave Tucker <dave@dtucker.co.uk>
9 months ago
aya = { path = "../../aya", version = "0.11.0", default-features = false }
aya-log = { path = "../../aya-log", version = "0.1.13", default-features = false }
aya-obj = { path = "../../aya-obj", version = "0.1.0", default-features = false }
integration-tests: enable logs Use test_log::test so setting RUST_LOG=aya=debug works and it's easier to debug failures.
1 year ago
env_logger = { workspace = true }
aya: Implement RingBuf This implements the userspace binding for RingBuf. Instead of streaming the samples as heap buffers, the process_ring function takes a callback to which we pass the event's byte region, roughly following [libbpf]'s API design. This avoids a copy and allows marking the consumer pointer in a timely manner. [libbpf]: https://github.com/libbpf/libbpf/blob/master/src/ringbuf.c Additionally, integration tests are added to demonstrate the usage of the new APIs and to ensure that they work end-to-end. Co-authored-by: William Findlay <william@williamfindlay.com> Co-authored-by: Tatsuyuki Ishi <ishitatsuyuki@gmail.com>
1 year ago
epoll = { workspace = true }
futures = { workspace = true, features = ["std"] }
cargo: Define dependencies on the workspace level This way we will avoid version mismatches and make differences in features across our crates clearer.
1 year ago
libc = { workspace = true }
log = { workspace = true }
test: add the possibility to run a test inside a network namespace For tests that do networking operations, this allows to have a clean-state network namespace and interfaces for each test. Mainly, this avoids "device or resource busy" errors when reusing the loopback interface across tests.
2 years ago
netns-rs = { workspace = true }
aya: Implement RingBuf This implements the userspace binding for RingBuf. Instead of streaming the samples as heap buffers, the process_ring function takes a callback to which we pass the event's byte region, roughly following [libbpf]'s API design. This avoids a copy and allows marking the consumer pointer in a timely manner. [libbpf]: https://github.com/libbpf/libbpf/blob/master/src/ringbuf.c Additionally, integration tests are added to demonstrate the usage of the new APIs and to ensure that they work end-to-end. Co-authored-by: William Findlay <william@williamfindlay.com> Co-authored-by: Tatsuyuki Ishi <ishitatsuyuki@gmail.com>
1 year ago
object = { workspace = true, features = ["elf", "read_core", "std"] }
rand = { workspace = true, features = ["std", "std_rng"] }
cargo: Define dependencies on the workspace level This way we will avoid version mismatches and make differences in features across our crates clearer.
1 year ago
rbpf = { workspace = true }
integration-test: Remove runtime toolchain deps Move the use of clang and llvm-objcopy from run-time to build-time. This allows the integration tests to run on VMs with simpler userlands. Create a new CI job to build the integration tests separately from running them. Ship them from that job to the runner job using github actions artifacts.
1 year ago
test-case = { workspace = true }
integration-tests: enable logs Use test_log::test so setting RUST_LOG=aya=debug works and it's easier to debug failures.
1 year ago
test-log = { workspace = true, features = ["log"] }
aya: Implement RingBuf This implements the userspace binding for RingBuf. Instead of streaming the samples as heap buffers, the process_ring function takes a callback to which we pass the event's byte region, roughly following [libbpf]'s API design. This avoids a copy and allows marking the consumer pointer in a timely manner. [libbpf]: https://github.com/libbpf/libbpf/blob/master/src/ringbuf.c Additionally, integration tests are added to demonstrate the usage of the new APIs and to ensure that they work end-to-end. Co-authored-by: William Findlay <william@williamfindlay.com> Co-authored-by: Tatsuyuki Ishi <ishitatsuyuki@gmail.com>
1 year ago
tokio = { workspace = true, features = ["macros", "rt-multi-thread", "time"] }
tests: add AF_XDP test using xdpilone
1 year ago
xdpilone = { workspace = true }
integration-test: compile Rust probes using build.rs
1 year ago
[build-dependencies]
cargo: Define dependencies on the workspace level This way we will avoid version mismatches and make differences in features across our crates clearer.
1 year ago
cargo_metadata = { workspace = true }
integration-test: build-dep on integration-ebpf Remove the manual dependency tracking machinery in integration-test/build.rs in favor of a build-dependency on integration-ebpf. This required adding an empty lib.rs to create the library target. This allows integration-test/build.rs to be ignorant of bpf-linker. Remove that in favor of the logic now in integration-ebpf.
1 year ago
# TODO(https://github.com/rust-lang/cargo/issues/12375): this should be an artifact dependency, but
# it's not possible to tell cargo to use `-Z build-std` to build it. We cargo-in-cargo in the build
# script to build this, but we want to teach cargo about the dependecy so that cache invalidation
# works properly.
#
# Note also that https://github.com/rust-lang/cargo/issues/10593 occurs when `target = ...` is added
# to an artifact dependency; it seems possible to work around that by setting `resolver = "1"` in
# Cargo.toml in the workspace root.
#
# Finally note that *any* usage of `artifact = ...` in *any* Cargo.toml in the workspace breaks
# workflows with stable cargo; stable cargo outright refuses to load manifests that use unstable
# features.
integration-ebpf = { path = "../integration-ebpf" }
cargo: Define dependencies on the workspace level This way we will avoid version mismatches and make differences in features across our crates clearer.
1 year ago
xtask = { workspace = true }