diff options
author | Martin Jansa <Martin.Jansa@gmail.com> | 2017-09-22 22:54:59 +0000 |
---|---|---|
committer | Martin Jansa <Martin.Jansa@gmail.com> | 2019-03-24 11:13:28 +0100 |
commit | 8a37431f60ac5fa8c04ceb08cba3448264c33fdb (patch) | |
tree | 14a93c46d4e8a3963965464389d528a38f5c4296 /scripts/oe-publish-sdk | |
parent | 91e3b2a762124bf5cf923654ef3a7c871b84c82f (diff) | |
download | openembedded-core-contrib-8a37431f60ac5fa8c04ceb08cba3448264c33fdb.tar.gz |
insane.bbclass: Add do_qa_pseudo function to check for common errors listed in pseudo.log
* we often see QA warnings like:
glibc-locale-2.26: glibc-locale: /glibc-binary-localedata-en-gb/usr/lib/locale/en_GB/LC_MEASUREMENT is owned by uid 3004, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
glibc-locale-2.26: glibc-locale: /glibc-binary-localedata-nn-no.iso-8859-1/usr/lib/locale/nn_NO.ISO-8859-1/LC_MEASUREMENT is owned by uid 3004, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
but we don't know the root cause of it.
* don't trigger error from '^inode mismatch'
* show parts of pseudo.log in console
many builds are executed in tmpfs, so I cannot check the pseudo.log later
* lower from error to warn as I hate all my builds reporting failure
just because of this pseudo debug
* add [qa_pseudo] on first line so that it's found correctly (the first line is most important
and package_qa_handle_error appends the error name at the end after last line)
* the only theory we currently have is that it's a bug in pseudo when
inode is being reused for different files, which is supported by
pseudo.log entries:
Good build:
pseudo$ grep -v "^path mismatch" pseudo.log
debug_logfile: fd 2
pid 7975 [parent 7974], doing new pid setup and server start
Setup complete, sending SIGUSR1 to pid 7974.
db cleanup for server shutdown, 17:33:58.787
memory-to-file backup complete, 17:33:58.787.
db cleanup finished, 17:33:58.787
Build with QA host-user-contaminated issue:
ERROR: foo-1.0.0-r0 do_package_qa: QA Issue: foo: file-with-wrong-UID is owned
by uid 2001, which is the same as the user running bitbake. This may be due to
host contamination [host-user-contaminated]
pseudo$ grep "file-with-wrong-UID" pseudo.log
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
creat ignored for existing file 'file-with-wrong-UID'.
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
path mismatch [1 link]: ino 13242270 db 'file-with-wrong-UID' req 'some-other-unrelated-file'.
creat for 'some-other-unrelated-file' replaces existing 13242270 ['file-with-wrong-UID'].
db cleanup for server shutdown, 02:16:23.685
memory-to-file backup complete, 02:16:23.685.
db cleanup finished, 02:16:23.685
And some-other-unrelated-file is really some different file, not just hardlink
to the same file from some different directory (like between WORKDIR and sysroot
other "path mismatch" entries show).
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Diffstat (limited to 'scripts/oe-publish-sdk')
0 files changed, 0 insertions, 0 deletions