On 22.02.22 18:50, Ross Burton wrote:
On Tue, 22 Feb 2022 at 17:01, Konrad Weihmann <kweihm...@outlook.com> 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
TBH I don't know - I (and Ralph confirmed that) see occasionally this
error from the original patch.
As I mentioned I lack the experience with sqlite to get to the bottom of
it - all I can say is that since the task lock had been merged I'm error
free in all the pipelines I monitor
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162183):
https://lists.openembedded.org/g/openembedded-core/message/162183
Mute This Topic: https://lists.openembedded.org/mt/88258164/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
