From: Patrick Ohly <patrick.ohly@intel.com>
To: Denys Zagorui <denys.zagorui@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] gzip: add ptest
Date: Fri, 10 Mar 2017 08:10:13 +0100 [thread overview]
Message-ID: <1489129813.7785.380.camel@intel.com> (raw)
In-Reply-To: <1489092518-25721-1-git-send-email-denys.zagorui@gmail.com>
On Thu, 2017-03-09 at 22:48 +0200, Denys Zagorui wrote:
> tests don't work with 'diff' and 'less' utils from busybox
I don't think that depending on diff and less is the right solution for
that problem, because then enabling testing will change the system that
is meant to be tested.
For example, suppose that the real system only has busybox and busybox
diff needs to work. That version of diff cannot be tested anymore with
IMAGE_FEATURES += "ptest-pkgs" because that will pull in gzip-ptest,
which then overrides the busybox diff.
Perhaps the tests can be fixed to work also with busybox, or the tests
can detect busybox and skip the part that depends on real diff and less?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2017-03-10 7:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 20:48 [PATCH] gzip: add ptest Denys Zagorui
2017-03-10 7:10 ` Patrick Ohly [this message]
[not found] ` <CACJ80St7+4KB+Tm6J=Gqmyc-UVxuky_9Qwu25kFwqJ68=TWKzw@mail.gmail.com>
2017-03-12 20:02 ` Denys Zagorui
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=1489129813.7785.380.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=denys.zagorui@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox