4 Commits (7a51127b24802256ac6a532f0cddf411ce10603d)

Author	SHA1	Message	Date
Tamir Duberstein	728a25d9d9	vscode: check all targets ... Now that building integration tests works out of the box, we can.	2 years ago
Dave Tucker	dc31e11691	Re-organize into a single workspace ... This commit moves the aya-log projects from the subtree and adds them to the main cargo workspace. It also brings the BPF crates into the workspace and moves the macro crates up a level since they aren't BPF code. Miri was disabled for aya-bpf as the previous config wasn't actually checking anything. CI, clippy, fmt and release configurations have all been adjusted appropriately. CI was not properly running for other supported arches which was also ixed here. Signed-off-by: Dave Tucker <dave@dtucker.co.uk>	3 years ago
Dave Tucker	79101e748a	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>	3 years ago
William Findlay	e115b72245	meta: fix rust-analyzer support for aya-bpf ... Ironically, we have the same issue here as in https://github.com/aya-rs/aya-template/pull/13/. This patch fixes this by explicitly defining the project layout for both vscode and neovim.	4 years ago