You need to look at configurations defined here: http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder-helper/tree/config.json and replicate them locally. Then you can reproduce the failures that the AB gets in those configurations.
Alex On Mon, 27 Apr 2020 at 18:25, Rahul Kumar <[email protected]> wrote: > Hi Richard, > > With this patch I am able to build core-image-minimal without any > Error/Warning in my system. > Can you please suggest to me, how can i reproduce this issue in my system > during build? > > *Thanks & Regards,* > Rahul Kumar > Software Engineer,Linux Solutions Engineering > Group,Montavista Software LLC > Email Id: [email protected] > <https://plus.google.com/+CodeTwoSoftware> > > > On Mon, Apr 27, 2020 at 8:39 PM Richard Purdie < > [email protected]> wrote: > >> On Fri, 2020-04-24 at 00:09 +0530, Rahul Kumar wrote: >> > Source: git://sourceware.org/git/bzip2-tests.git >> > Type: Enhancement >> > Description: >> > bzip2 now has a test suite available at >> > git://sourceware.org/git/bzip2-tests.git. >> > >> > This is a collection of "interesting" .bz2 files that can be used to >> > test bzip2 works correctly. They come from different projects. >> > >> > Some files are deliberately bad, and are use to see how bzip2 handles >> > corrupt files. They are explicitly not intended to decompress >> > correctly, >> > but to catch errors in bzip2 trying to deal with deliberately bad >> > data. >> > All such files have a name ending in .bz2.bad. >> > >> > All non-bad files end in bz2. And should come with a .md5 file for >> > the original input file. The .md5 file is used to check that bzip2 >> > could correctly decompress the file. The original (non-compressed) >> > files are deliberately not checked in. >> > >> > It will by default test with the command 'bzip2', running under >> > valgrind (if installed on the system). >> > >> > For each .bz2 file found it is decompressed, recompressed and >> > decompressed again. Once with the default bzip2 settings and >> > once in --small (-s) mode. >> > >> > For each .bz2.bad file decompression is tried twice also. In >> > default mode and small mode. The bzip2 binary is expected to >> > return either 1 or 2 as exit status. Any other exit code is >> > interpreted as failure. >> >> I did try running this on the autobuilder. There are a few issues. >> >> https://autobuilder.yoctoproject.org/typhoon/#/builders/62/builds/1816 >> step1b >> <https://autobuilder.yoctoproject.org/typhoon/#/builders/62/builds/1816step1b>: >> ERROR: bzip2-1.0.8-r0 do_package_qa: QA Issue: >> /usr/lib/bzip2/ptest/bzip2-tests/.git/hooks/fsmonitor-watchman.sample >> contained in package bzip2-ptest requires /usr/bin/perl, but no providers >> found in RDEPENDS_bzip2-ptest? [file-rdeps] >> step1b: ERROR: bzip2-1.0.8-r0 do_package_qa: QA run found fatal errors. >> Please consider fixing them. >> >> also, the new license (GPLv3) causes problems: >> >> https://autobuilder.yoctoproject.org/typhoon/#/builders/75/builds/1814 >> >> Cheers, >> >> Richard >> >> >> >> >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#137527): https://lists.openembedded.org/g/openembedded-core/message/137527 Mute This Topic: https://lists.openembedded.org/mt/73224911/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
