mbox series

[0/3] yocto-check-layer: Faster BSP checks over many machines

Message ID 20261017225656.680168-1-otavio@ossystems.com.br
Headers show
Series yocto-check-layer: Faster BSP checks over many machines | expand

Message

Otavio Salvador Oct. 17, 2026, 10:56 p.m. UTC 
Checking a BSP layer over many machines is dominated by world signature
dumps: two per machine, plus four for the common tests. In CI the
machines are usually split into several runs, which repeat the common
tests and their dumps in each.

This series lets such runs select their tests and stops repeating a dump
whose result is already known:

- --run-tests, as in oe-test, so the common tests run once and the BSP
  tests in each group of machines;
- no initial (pre-layer) dump when test_signatures is not selected;
- reuse of a successful dump when the same one is asked for again,
  which test_world and test_machine_world do after test_signatures and
  test_machine_signatures. Failed dumps are not reused, so the world
  tests still report them.

A full run over N machines goes from 2N+4 dumps to N+3; a split run
does 3 dumps for the common tests and N for the BSP ones. Tested on
meta-freescale with two machines: 5 dumps instead of 8 with identical
results, and a recipe breaking world on one machine still fails
test_machine_world for that machine only.

This came out of the check-layer CI work for meta-freescale, which
currently does the same through a wrapper around yocto-check-layer.

Otavio Salvador (3):
  yocto-check-layer: Add --run-tests to select the tests to run
  yocto-check-layer: Skip initial signatures unless test_signatures runs
  checklayer: Reuse signatures of an identical successful world dump

 scripts/lib/checklayer/__init__.py | 13 ++++++++++++-
 scripts/yocto-check-layer          | 12 ++++++++----
 2 files changed, 20 insertions(+), 5 deletions(-)