On Thu, 2023-10-05 at 10:47 +0200, Alexander Kanavin wrote: > On Wed, 4 Oct 2023 at 14:57, Yoann Congal <[email protected]> wrote: > > Currently, this check find: > > * 309 unimplemented ptest in oe-core/meta-poky/meta-yocto-bsp > > * 827 unimplemented ptest in meta-openembedded > > Does this mean there will be this many warnings in everyone's builds? > If so, this cannot be enabled by default; any new QA warning must > either not be triggered at all on the current revision (and is added > specifically to prevent regressions), or come with a realistic plan to > address the warnings. Implementing hundreds of ptests in a short time > frame is not realistic. > > On the other hand, the output could go into some kind of report, I'm > just not sure which one.
It isn't enabled in default builds and can't be for the reason you mention so I think the intention is that we can do reporting using this periodically. Ultimately we might have it as a new "log" or "report" level and just generate reports during the build. We did used to do that for previous "insane" tests. We just need to think about how that would work with sstate (warnings are already an issue with sstate). Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#188709): https://lists.openembedded.org/g/openembedded-core/message/188709 Mute This Topic: https://lists.openembedded.org/mt/101754134/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
