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.
dependabot/github_actions/github-actions-47e489e734
dependabot/cargo/cargo-crates-c0234dbee0
main
pr/Billy99/974
linker-bindep
fix-verifier-blixt
revert-461-main
gh-pages
ci
perf-event
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
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '34d1d7a9d7'
${ noResults }
aya/test/integration-test/Cargo.toml

38 lines
1.4 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"
Change from Rust edition 2018 to 2021 Rust 2021 adds more core prelude imports, including `TryFrom` and `TryInto`. Signed-off-by: Michal Rostecki <vadorovsky@gmail.com>
2 years ago
edition = "2021"
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
publish = false
[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
anyhow = { workspace = true, default-features = true }
assert_matches = { workspace = true }
aya = { workspace = true }
aya-log = { workspace = true }
aya-obj = { workspace = true }
libc = { workspace = true }
log = { workspace = true }
object = { workspace = true }
rbpf = { workspace = true }
tokio = { workspace = true, default-features = false, features = [
Remove "async" feature This feature is equivalent to async_tokio || async_std; removing it avoids warnings emitted during `cargo hack check --feature-powerset` where async is selected without either of the other features. Use cargo hack to ensure clippy runs on the powerset of features.
1 year ago
"macros",
"time",
] }
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 }