mirror of
https://github.com/linux-msm/bootrr.git
synced 2026-02-25 13:12:03 -08:00
04922d1bd7
In the typical scenario where the bootrr cpio archive is concatenated onto some ramdisk, attributes of this cpio archive will overwrite those previously extracted. When used in combination with a ramdisk with systemd, this results in many services failing to start, because the namespaced services does not have permission to open e.g. / Fix this my overriding the owner and group. Signed-off-by: Bjorn Andersson <quic_bjorande@quicinc.com>
Bootrr
A sanity checker for boards under automated test on LAVA.
Before running the tests for your software stack on LAVA, you really want to ensure that the basics are in place.
Testing that all the expected hardware is detected and that modules and firmwares can be loaded catches some very common kind of regressions: for instance, when renaming identifiers it is often the case that firmware blobs no longer get loaded since their location needs to be updated accordingly.
This repository contains:
- static board descriptions that list what to expect for each specific board type
- helpers to inspect the current system and compare it against the static board description for it
- the
bootrrscript to automatically detect the current board and run the matching tests
The output is in a format meant to be directly parsed by LAVA.
Install
$ make prefix=/usr/local DESTDIR=/ install
Usage
$ bootrr
<LAVA_SIGNAL_TESTCASE TEST_CASE_ID=deferred-probe-empty RESULT=skip>
<LAVA_SIGNAL_TESTCASE TEST_CASE_ID=all-cpus-are-online RESULT=pass>
Related Efforts
- LAVA - A continuous integration system for deploying operating systems onto physical and virtual hardware for running tests.
- KernelCI - Community-led test system focused on the upstream Linux kernel.
License
BSD-3-Clause