]> code.ossystems Code Review - openembedded-core.git/commit
ptest: add an option to enforce a failure (e.g. ptests are required to pass)
authorAlexander Kanavin <alex.kanavin@gmail.com>
Sun, 23 Feb 2020 13:52:31 +0000 (14:52 +0100)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Tue, 25 Feb 2020 10:41:15 +0000 (10:41 +0000)
commit102afcc7ea7d7673183f272a29ab233084ad168b
tree977c4b6fc056fd3fc94d3987bc9dd2f2fcf85be1
parent4abb2f270ba61e99993e53d292bcf5310a59dc19
ptest: add an option to enforce a failure (e.g. ptests are required to pass)

This can be useful with a more specific, targeted and robust set of ptest
packages; the benefit is that ptest regressions are caught as they happen
and can be more easily traced to changes that caused them.

The existing AB ptest image continues to be expected to fail, my observation
of the AB runs is that the full set of ptests is not robust enough
(particularly around socket/network related tests) and sporadically fails
in random places. This can probably be addressed by making ptests exclusive
to a worker (e.g. there is no other workload happening at the same time as
ptests).

Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/lib/oeqa/runtime/cases/ptest.py
meta/recipes-sato/images/core-image-sato-sdk-ptest.bb