Come to think of it, maybe it's okay in this situation to actually remove OEHasPackage - the test will simply always run, and will still fail if the package is absent, but the failure would be less specific than a missing package.
Alex On Mon, 15 Jun 2020 at 18:41, Alexander Kanavin via lists.openembedded.org <[email protected]> wrote: > On Mon, 15 Jun 2020 at 16:02, Richard Purdie < > [email protected]> wrote: > >> I can see the use case, I'm a bit torn on whether we should fail in >> these cases, or whether we should enourage people to check the tests >> they expected to run really did. >> >> With the complexity on the autobuilder we've had to rely on the latter, >> comparing that all tests that ran previously, still run. >> > > Do we have some kind of tooling to check that tests that are expected to > run, did run, and were not skipped? > This patch came from our internal situation where due to debian renaming, > @OEHasPackage started skipping tests > that it should not have. It wasn't immediately noticed - test logs are > hidden inside the build logs, and the build logs are not > usually looked at if the overall build does not fail. > > People were very baffled by that, and it took 'yocto experts' (Konrad :) > to sort the issue. > > Alex > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#139508): https://lists.openembedded.org/g/openembedded-core/message/139508 Mute This Topic: https://lists.openembedded.org/mt/74855190/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
