Hello, Please take into account that the VEX class is using the same file names for results as the cve-check. The reason was to avoid duplication of all intermediary files, and also the final files. This was a design decision, as not many people are expected to switch between cve-check and vex classes, instead keep one.
Kind regards, Marta On Thu, Jan 29, 2026 at 5:34 PM vboudevin via lists.openembedded.org <[email protected]> wrote: > Hello Daniel, > > I made some tests with the new vex class. I may be wrong, but it doesn't > seem like an issue linked with improve_kernel_cve_report bbclass. > > I tried to clean the build, remove "inherit improve_kernel_cve_report", > and keep "INHERIT += "vex"" . But, the cve-summary file is still empty > after the rebuild. > > If I change back to "cve-check" (still without improve_kernel_cve_report > class) cve-summary seems correct and not empty. > > It looks more like a vex class issue. Also, VEX does not seem to recreate > a new .json file at every build, which is strange. > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#230337): https://lists.openembedded.org/g/openembedded-core/message/230337 Mute This Topic: https://lists.openembedded.org/mt/117510774/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
