test: add sanitizer integration pipeline

Add a dedicated integration test to run vmm Rust integration tests under ASAN and wire a Buildkite pipeline generator for periodic sanitizer runs.

Also document the run command and harden tools/test.sh for local runs under set -u by guarding BUILDKITE variable access.

Signed-off-by: Aaron Ang <aaron.angyd@gmail.com>

Author: aaron-ang

.buildkite/pipeline_sanitizers.py

@@ -0,0 +1,19 @@
+#!/usr/bin/env python3
+# Copyright 2026 Amazon.com, Inc. or its affiliates. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+
+"""Generate Buildkite pipelines dynamically."""
+
+from common import BKPipeline
+
+pipeline = BKPipeline(with_build_step=False)
+
+pipeline.build_group_per_arch(
+    "sanitizers",
+    pipeline.devtool_test(
+        devtool_opts="--no-build",
+        pytest_opts="integration_tests/build/test_sanitizers.py",
+    ),
+)
+
+print(pipeline.to_json())

tests/README.md

@@ -111,6 +111,18 @@ Unlike unit tests, Rust integration tests are each run in a separate process.
 To learn more about Rust integration test, see
 [the Rust book](https://doc.rust-lang.org/book/ch11-03-test-organization.html#integration-tests).
 
+## Sanitizer Runs
+
+Firecracker also has a dedicated build test that runs Rust integration tests
+under sanitizers:
+
+```bash
+tools/devtool -y test -- -m nonci integration_tests/build/test_sanitizers.py
+```
+
+The Buildkite sanitizer pipeline is generated by
+[`pipeline_sanitizers.py`](../.buildkite/pipeline_sanitizers.py).
+
 ## A/B-Tests
 
 A/B-Testing is a testing strategy where some test function is executed twice in

tests/integration_tests/build/test_sanitizers.py

@@ -0,0 +1,40 @@
+# Copyright 2026 Amazon.com, Inc. or its affiliates. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+"""Run Rust integration tests under sanitizers."""
+
+import platform
+from uuid import uuid4
+
+import pytest
+
+from framework import defs
+from host_tools.cargo_build import cargo
+
+TARGET = f"{platform.machine()}-unknown-linux-gnu"
+SANITIZERS = ("address",)
+REPO_ROOT = defs.FC_WORKSPACE_DIR
+
+
+@pytest.mark.nonci
+@pytest.mark.timeout(3600)
+@pytest.mark.parametrize("sanitizer", SANITIZERS)
+def test_rust_integration_tests_under_sanitizer(sanitizer):
+    """Run vmm Rust integration tests under the specified sanitizer."""
+    target_flag_var = f"CARGO_TARGET_{TARGET.upper().replace('-', '_')}_RUSTFLAGS"
+    target_dir = (
+        defs.LOCAL_BUILD_PATH
+        / "cargo_target"
+        / "sanitizers"
+        / (f"{sanitizer}-{uuid4().hex}")
+    )
+    cargo(
+        "test",
+        f"--target {TARGET} -p vmm --test integration_tests",
+        "--test-threads=1",
+        nightly=True,
+        cwd=str(REPO_ROOT),
+        env={
+            "CARGO_TARGET_DIR": str(target_dir),
+            target_flag_var: f"-Zsanitizer={sanitizer}",
+        },
+    )

tools/test.sh

@@ -53,7 +53,7 @@ export PYTEST_ADDOPTS="${PYTEST_ADDOPTS:-} --pdbcls=IPython.terminal.debugger:Te
 
 # if the tests failed and we are running in CI, print some disk usage stats
 # to help troubleshooting
-if [ $ret != 0 ] && [ "$BUILDKITE" == "true" ]; then
+if [ $ret != 0 ] && [ "${BUILDKITE:-false}" == "true" ]; then
     df -ih
     df -h
     du -h / 2>/dev/null |sort -h |tail -32