pseudo database integrity checking
Quoted 6 lines · Richard Purdie via lists.openembedded.org
c) We could add specialist code to bitbake such that when a fakeroot worker exits with 134, we dump the tail end of the pseudo log if present. That doens't directly fix the issue but would help users debug problems. This does come at a cost of making the bitbake code pseudo specific.
We did already implement c). It showed up in some cases locally where pseudo was aborting but not others so I need to really work out why it isn't consistent :/.
Cheers,
Richard