From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
Vasyl Vavrychuk <vvavrychuk@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] runqemu: Change virtio-vga to virtio-gpu.
Date: Sun, 01 Nov 2020 12:27:50 +0000 [thread overview]
Message-ID: <ef608819d2cb9129ae2783ecf6040b77cc0cf4e0.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj_7KWx7h=LGJd_zwN3gNEcRY1_i4cOriciQBxCns5mvKA@mail.gmail.com>
On Sat, 2020-10-31 at 13:27 +0100, Alexander Kanavin wrote:
> I think you first need to set up a build directory to use sstate-
> cache in some common location, then build-st will pick it up, and you
> can then easily delete it without destroying the cache.
You can do something like the patch below. I would warn that the tests
assume clean directories so you have to be careful doing this though.
Cheers,
Richard
Subject: HACK:selftest/context: Allow reuse of existing build directory
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
meta/lib/oeqa/selftest/context.py | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/meta/lib/oeqa/selftest/context.py b/meta/lib/oeqa/selftest/context.py
index dd3609c1d6..3a2447d026 100644
--- a/meta/lib/oeqa/selftest/context.py
+++ b/meta/lib/oeqa/selftest/context.py
@@ -73,12 +73,16 @@ class OESelftestTestContext(OETestContext):
newselftestdir = newbuilddir + "/meta-selftest"
if os.path.exists(newbuilddir):
- self.logger.error("Build directory %s already exists, aborting" % newbuilddir)
- sys.exit(1)
+ # self.logger.error("Build directory %s already exists, aborting" % newbuilddir)
+ # sys.exit(1)
+ bb.utils.prunedir(newselftestdir)
+ bb.utils.prunedir(newbuilddir + "/conf")
+
+ if not os.path.exists(newbuilddir):
+ bb.utils.mkdirhier(newbuilddir)
+ oe.path.copytree(builddir + "/cache", newbuilddir + "/cache")
- bb.utils.mkdirhier(newbuilddir)
oe.path.copytree(builddir + "/conf", newbuilddir + "/conf")
- oe.path.copytree(builddir + "/cache", newbuilddir + "/cache")
oe.path.copytree(selftestdir, newselftestdir)
for e in os.environ:
next prev parent reply other threads:[~2020-11-01 12:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 20:15 [PATCH] runqemu: Change virtio-vga to virtio-gpu Vasyl Vavrychuk
2020-08-30 20:43 ` [OE-core] " Alexander Kanavin
2020-10-30 12:38 ` Vasyl Vavrychuk
2020-10-31 12:27 ` Alexander Kanavin
2020-11-01 12:27 ` Richard Purdie [this message]
2020-11-05 9:52 ` Vasyl Vavrychuk
2020-11-05 9:56 ` Alexander Kanavin
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=ef608819d2cb9129ae2783ecf6040b77cc0cf4e0.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=vvavrychuk@gmail.com \
/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