feat: skip tests requiring sudo if GITHUB_ACTIONS is not set

Also add a rebuild trigger to make it easier to run
GITHUB_ACTIONS=1 cargo test` locally.

We could have a better trigger, but this will do for now.

Author: GuillaumeLagrange

AGENTS.md

@@ -17,21 +17,16 @@ cargo build
 # Build in release mode
 cargo build --release
 
-# Run tests (prefer nextest if available)
-cargo nextest run  # preferred if installed
-cargo test         # fallback if nextest is not available
+# Run tests
+cargo test
 
 # Run specific test
-cargo nextest run <test_name>  # with nextest
-cargo test <test_name>         # with cargo test
+cargo test <test_name>
 
 # Run tests with output
-cargo nextest run --nocapture  # with nextest
-cargo test -- --nocapture      # with cargo test
+cargo test -- -nocapture
 ```
 
-**Note**: Always check if `cargo nextest` is available first (with `cargo nextest --version` or `which cargo-nextest`). If available, use it instead of `cargo test` as it provides faster and more reliable test execution.
-
 ### Running the Application
 
 ```bash
@@ -99,7 +94,7 @@ The core functionality for running benchmarks:
 
 The project uses:
 
-- `cargo nextest` (preferred) or standard Rust `cargo test`
+- `cargo test`
 - `insta` for snapshot testing
 - `rstest` for parameterized tests
 - `temp-env` for environment variable testing
@@ -108,5 +103,4 @@ Test files include snapshots in `snapshots/` directories for various run environ
 
 **Important**:
 
-- Always prefer `cargo nextest run` over `cargo test` when running tests, as it provides better performance and reliability.
-- Some walltime executor tests require `sudo` access and will fail in non-interactive environments (e.g., `test_walltime_executor::*`). These failures are expected if sudo is not available.
+- Some tests require `sudo` access. They are skipped by default unless the `GITHUB_ACTIONS` env var is set.

CONTRIBUTING.md

@@ -96,3 +96,7 @@ This ensures only stable runner releases are marked as "latest" in GitHub.
 ## Known issue
 
 - If one of the crates is currenlty in beta version, for example the runner is in beta version 4.4.2-beta.1, any alpha release will fail for the any crate, saying that only minor, major or patch releases is supported.
+
+## Testing
+
+- Some tests require `sudo` access. They are skipped by default unless the `GITHUB_ACTIONS` env var is set.

build.rs

@@ -0,0 +1,6 @@
+fn main() {
+    // Force a rebuild of the test target to be able to run the full test suite locally just by
+    // setting GITHUB_ACTIONS=1 in the environment.
+    // This is because `test_with` is evaluated at build time
+    println!("cargo::rerun-if-env-changed=GITHUB_ACTIONS");
+}

crates/memtrack/build.rs

@@ -3,6 +3,11 @@ use std::{env, path::PathBuf};
 
 #[cfg(feature = "ebpf")]
 fn build_ebpf() {
+    // Force a rebuild of the test target to be able to run the full test suite locally just by
+    // setting GITHUB_ACTIONS=1 in the environment.
+    // This is because `test_with` is evaluated at build time
+    println!("cargo::rerun-if-env-changed=GITHUB_ACTIONS");
+
     use libbpf_cargo::SkeletonBuilder;
 
     println!("cargo:rerun-if-changed=src/ebpf/c");

src/executor/tests.rs

@@ -1,9 +1,6 @@
 use super::Config;
 use crate::executor::ExecutionContext;
 use crate::executor::Executor;
-use crate::executor::memory::executor::MemoryExecutor;
-use crate::executor::valgrind::executor::ValgrindExecutor;
-use crate::executor::wall_time::executor::WallTimeExecutor;
 use crate::runner_mode::RunnerMode;
 use crate::system::SystemInfo;
 use rstest_reuse::{self, *};
@@ -109,16 +106,6 @@ const ENV_TESTS: [(&str, &str); 8] = [
 #[case(TESTS[5])]
 fn test_cases(#[case] cmd: &str) {}
 
-// Exec-harness currently does not support the inline multi command scripts
-#[template]
-#[rstest::rstest]
-#[case(TESTS[0])]
-#[case(TESTS[1])]
-#[case(TESTS[2])]
-fn exec_harness_test_cases() -> Vec<&'static str> {
-    EXEC_HARNESS_COMMANDS.to_vec()
-}
-
 #[template]
 #[rstest::rstest]
 #[case(ENV_TESTS[0])]
@@ -182,6 +169,7 @@ async fn acquire_bpf_instrumentation_lock() -> SemaphorePermit<'static> {
 
 mod valgrind {
     use super::*;
+    use crate::executor::valgrind::executor::ValgrindExecutor;
 
     async fn get_valgrind_executor() -> (SemaphorePermit<'static>, &'static ValgrindExecutor) {
         static VALGRIND_EXECUTOR: OnceCell<ValgrindExecutor> = OnceCell::const_new();
@@ -240,8 +228,10 @@ mod valgrind {
     }
 }
 
+#[test_with::env(GITHUB_ACTIONS)]
 mod walltime {
     use super::*;
+    use crate::executor::wall_time::executor::WallTimeExecutor;
 
     async fn get_walltime_executor() -> (SemaphorePermit<'static>, WallTimeExecutor) {
         static WALLTIME_INIT: OnceCell<()> = OnceCell::const_new();
@@ -358,6 +348,16 @@ fi
         })
         .await;
     }
+    //
+    // Exec-harness currently does not support the inline multi command scripts
+    #[template]
+    #[rstest::rstest]
+    #[case(TESTS[0])]
+    #[case(TESTS[1])]
+    #[case(TESTS[2])]
+    fn exec_harness_test_cases() -> Vec<&'static str> {
+        EXEC_HARNESS_COMMANDS.to_vec()
+    }
 
     // Ensure that the walltime executor works with the exec-harness
     #[apply(exec_harness_test_cases)]
@@ -391,8 +391,10 @@ fi
     }
 }
 
+#[test_with::env(GITHUB_ACTIONS)]
 mod memory {
     use super::*;
+    use crate::executor::memory::executor::MemoryExecutor;
 
     async fn get_memory_executor() -> (
         SemaphorePermit<'static>,