On Tue, 22 Feb 2022 at 17:01, Konrad Weihmann <[email protected]> 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. > 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.
Hang on - surely the cve_check tasks are read-only, so why do we need to lock the database? Ross
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#162182): https://lists.openembedded.org/g/openembedded-core/message/162182 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]] -=-=-=-=-=-=-=-=-=-=-=-
