On Sun, 2024-10-13 at 08:26 +0100, Richard Purdie via lists.openembedded.org wrote: > On Fri, 2024-10-11 at 13:24 +0200, Marta Rybczynska wrote: > > > > > > On Fri, Oct 11, 2024 at 1:19 PM Richard Purdie > > <[email protected]> wrote: > > > On Fri, 2024-10-11 at 13:17 +0200, Marta Rybczynska wrote: > > > > > > > > On Fri, Oct 11, 2024 at 1:02 PM Richard Purdie via > > > > lists.openembedded.org > > > > <[email protected]> > > > > wrote: > > > > > > > > > > I now do have an example of a corrupted database: > > > > > > > > > > https://valkyrie.yocto.io/pub/shared-failure-data/nvdcve_2-1.db > > > > > > > > > > I'm not sure why this is happening but the older releases are > > > > > all > > > > > accessing the DB over NFS which makes me nervous. We're > > > > > seeing a > > > > > lot of > > > > > failures on the new cluster, hopefully this will help isolate > > > > > the > > > > > problem. > > > > > > > > > > > > > > > > > The database isn't completely corrupted, it looks like it is > > > > partial, > > > > however. What was the error > > > > that you got in that build? Any or just strange results? I'm > > > > running > > > > a verification vs a fresh database. > > > > > > https://valkyrie.yoctoproject.org/#/builders/23/builds/238/steps/14/logs/stdio > > > > > > Exception: sqlite3.DatabaseError: database disk image is > > > malformed > > > > > > > > > > > > Managed to get the same error with the sqlite command line. > > > I merged this patch as it would rule out a lot of things.
It looks like I didn't do this. I will do so, then we can rule out a few things. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#205785): https://lists.openembedded.org/g/openembedded-core/message/205785 Mute This Topic: https://lists.openembedded.org/mt/108946499/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
