Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Chris Larson <clarson@kergoth.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/4] Script and layer for running tests
Date: Thu, 28 Nov 2013 22:30:44 +0000	[thread overview]
Message-ID: <1468986.biIYlcqkQR@helios> (raw)
In-Reply-To: <CABcZAN=Tym_ZkCB4ihdJrQ0sqU-Kw9GU6vER5f2viKoxBWntdg@mail.gmail.com>

On Thursday 28 November 2013 13:29:32 Chris Larson wrote:
> On Thu, Nov 28, 2013 at 3:17 AM, Paul Eggleton <
> paul.eggleton@linux.intel.com> wrote:
> > On Wednesday 27 November 2013 11:42:06 Chris Larson wrote:
> > > Will this have its own repository like all the other poky integrated
> > > layers? It really should, in my opinion.
> > 
> > It really needs to stay in the same place as the tests that rely on it;
> > they can't work without it. It might be suggested that the tests should go
> > elsewhere with them; but I don't think that would make sense - we want
> > people to be able to run these tests easily if they make changes to OE-
> > Core to check if they have caused any regressions.
> > 
> > If you have a look at the layer, there's not a lot in it, and I wouldn't
> > expect a lot to be added in future. One possible change would be to just
> > have the layer created on the fly in some temporary directory by the tests
> > themselves, rather than having it in the repository; on the other hand it
> > does make it a bit more difficult to look into outside of the test
> > environment.
> 
> I understand what you’re saying, but if this script is supposed to be
> generally useful for OE/Yocto, not just Poky, then the poky repository
> shouldn’t be its definitive location.

Poky isn't its definitive location, it has been sent as a pull request to the 
OE-Core mailing list to be applied on top of OE-Core.

> Further, patches against oe-core should be submitted against the oe-core
> repository, not the poky repository, and anything poky specific should go to
> the poky list.

Point taken, but there isn't actually anything poky-specific in this series. 
Can we please concentrate on the content of the patches?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


      reply	other threads:[~2013-11-28 22:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-27 17:08 [PATCH 0/4] Script and layer for running tests Stefan Stanacar
2013-11-27 17:08 ` [PATCH 1/4] scripts/oe-selftest: script to run builds as unittest against bitbake or various scripts Stefan Stanacar
2013-11-27 17:08 ` [PATCH 2/4] meta-selftest: create a new test layer to be used by oe-selftest script Stefan Stanacar
2013-11-27 17:08 ` [PATCH 3/4] lib/oeqa/selftest: buildoptions.py: add simple image build tests Stefan Stanacar
2013-11-27 17:08 ` [PATCH 4/4] lib/oeqa/selftest: add test modules for expected bitbake output and bitbake-layers Stefan Stanacar
2013-11-27 18:42 ` [PATCH 0/4] Script and layer for running tests Chris Larson
2013-11-28 10:17   ` Paul Eggleton
2013-11-28 20:29     ` Chris Larson
2013-11-28 22:30       ` Paul Eggleton [this message]

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=1468986.biIYlcqkQR@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=clarson@kergoth.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