On Mon, 18 Sept 2023 at 10:28, [email protected] <[email protected]> wrote: > Thanks for your reply. > There are two ways to add markers. Which one is better? > 1. add one marker for the hole test of tar (as your suggestion) > 2. add markers(PASS, FAIL, SKIP) for every case > sample: > PASS: 1: tar version > FAIL: 5: TAR_OPTIONS with string arguments > SKIP: 11: --pax-option compatibility
I looked into why the test suite doesn't print those markers to begin with (GNU items usually do when they use libcheck). It seems that tests/testsuite is pre-generated with a different thing called 'autotest' that doesn't print them. You need to regenerate the file with autotest from from the native sysroot (provided by yocto), which is patched to print the markers: https://git.yoctoproject.org/poky/tree/meta/recipes-devtools/autoconf/autoconf/autotest-automake-result-format.patch and then use --am-fmt option with testsuite so they get printed. > When try to run 'bitbake -c testimage core-image-ptest-tar' command , my > compiling env can not find the testimage task. (ERROR: Task do_testimage does > not exist for target core-image-ptest-tar) > Maybe my compiling env has problems, so could you show me the correct steps > for running the command? local.conf should contain IMAGE_CLASSES += "testimage" You might already have it there, just commented out. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#187822): https://lists.openembedded.org/g/openembedded-core/message/187822 Mute This Topic: https://lists.openembedded.org/mt/101372466/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
