firecracker-microvm/firecracker

[Tests] Periodically run Firecracker integration tests under sanitizers

Open

#1662 opened on Mar 9, 2020

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Rust (34,348 stars) (2,393 forks)batch import
Good first issueStatus: ParkedType: Enhancement

Description

This issue does not include a description.

Contributor guide

Tech stack
rustdocker
Domain
testing
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Rust programmingFirecracker architectureSanitizersCI/CD knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Investigate current integration test setup in Firecracker's CI (likely in .buildkite or similar). Look for existing test scripts that run under sanitizers. Review previous discussions in the issue comments. Consider adding a periodic job to run tests with AddressSanitizer and other sanitizers enabled.