On Tue, Feb 22, 2022 at 06:01:00PM +0100, Konrad Weihmann wrote:
This is somehow expected from my side tbh - as the lock file disables any kind of parallelism - so just one instance of cve-check-task can run at a time.
That likely explains why the loadavg is only around 1 during cve-check.
One thing that came to my mind is to move the created CVE_CHECK-sqlite db into the recipe-sysroot before running the task (currently it resides in DL_DIR), so each task would run on its own copy of the db - that would avoid having multiple access call to the same file while enabling us to remove the arbitrary task lock.
I actually do something like this manually - in local.conf for each of my builds, I set CVE_CHECK_DB_DIR to a unique subdirectory within $DL_DIR. And I still see the occasional build failure due to "database in use".
Ralph
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#162181): https://lists.openembedded.org/g/openembedded-core/message/162181 Mute This Topic: https://lists.openembedded.org/mt/88258164/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
