All of lore.kernel.org
 help / color / mirror / Atom feed
From: "qiutt@fujitsu.com" <qiutt@fujitsu.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V3] tar: add ptest support
Date: Mon, 18 Sep 2023 01:28:23 -0700	[thread overview]
Message-ID: <31570.1695025703079386511@lists.openembedded.org> (raw)
In-Reply-To: <CANNYZj8T8_iW0mh4ct1OX33cxihSE0O2bZOzG3ra1GTy08w-fw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]

Hi, Alex

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

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 c ould you show me the correct steps for running the command ?

my steps :
1. download bitbake and install
cd ${WORK_DIR}
git clone https://git.openembedded.org/bitbake bitbake export BITBAKEDIR=${WORK_DIR}/bitbake/
2. download openembedded-core and apply this patch
git clone https://git.openembedded.org/openembedded-core oe-core
cd oe-core
patch -p1 < ${THIS_PATCH}
3. compile image
source ./oe-init-build-env
echo 'DISTRO_FEATURES:append = " ptest"' >>  conf/local.conf
bitbake core-image-ptest-tar
4. run command
bitbake -c testimage core-image-ptest-tar

[-- Attachment #2: Type: text/html, Size: 2644 bytes --]

  reply	other threads:[~2023-09-18  8:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15  2:26 [PATCH V3] tar: add ptest support qiutt
2023-09-15  6:12 ` [OE-core] " Alexander Kanavin
2023-09-18  8:28   ` qiutt [this message]
2023-09-18  9:32     ` Alexander Kanavin
2023-09-19  0:31       ` qiutt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=31570.1695025703079386511@lists.openembedded.org \
    --to=qiutt@fujitsu.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.