summaryrefslogtreecommitdiffstats
path: root/meta/lib/patchtest/repo.py
diff options
context:
space:
mode:
authorAlexander Kanavin <alex@linutronix.de>2025-09-29 14:56:08 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2025-10-09 22:05:17 +0100
commit7130566a978c92cb4cfae164afcaa7301dabb07a (patch)
treeb4f5a1f2334903fd0bbae9b3251e668100b2bab1 /meta/lib/patchtest/repo.py
parent04fd44cfc0c620653565bdd9592b92ce431a565f (diff)
downloadpoky-7130566a978c92cb4cfae164afcaa7301dabb07a.tar.gz
bitbake: bitbake-setup: add tests to bitbake-selftest
Run like this: alex@Zen2:/srv/work/alex/bitbake$ bin/bitbake-selftest -v bb.tests.setup test_setup (bb.tests.setup.BitbakeSetupTest.test_setup) ... ok ---------------------------------------------------------------------- Ran 1 test in 9.223s OK The test does a basic run-through of init, then status/update on an unchanged configuration, then status/update on a configuration changed via new commits to the test layer, then status/update on configuration changed via the top level json config file. Note that nothing whatsoever is fetched from the network; the test relies entirely on synthetic data contained inside itself, including minimal stubs for oe-setup-build and bitbake-config-build. This data is used to create temporary git repositories then clone them via local filesystem URIs. Later on this can be supplemented by an oe-selftest that tests bitbake-setup against real config files in the official configuration repository and real layers, templates and fragments. (Bitbake rev: 74e0bbe2fb7341f101f358c27da76e4891c068ae) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/lib/patchtest/repo.py')
0 files changed, 0 insertions, 0 deletions