From: Martin Jansa <martin.jansa@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: Chris Larson <clarson@kergoth.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCHv4] scripts/sstate-sysroot-cruft.sh: add simple script to find files in sysroots not tracked by sstate
Date: Thu, 15 Nov 2012 18:03:40 +0100 [thread overview]
Message-ID: <20121115170340.GD17521@jama.jama.net> (raw)
In-Reply-To: <2167600.lqqak59AbM@helios>
[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]
On Thu, Nov 15, 2012 at 04:49:01PM +0000, Paul Eggleton wrote:
> On Thursday 15 November 2012 17:19:07 Martin Jansa wrote:
> > I didn't want to use bitbake -e, so that this script can be executed
> > when some other bitbake process is running.
>
> You really should not be trying to touch anything under TMPDIR let alone
> sstate files while bitbake is actually running against that same directory. I'm
> not sure why you would want to though...
While running builds for 8 MACHINEs in for loop I find it usefull to
test one sysroot (from 1st MACHINE already built) while keeping
build for remaining machines running for rest of night and sometimes
following days..
At least that was my use-case when I wrote this script..
Yes I could have execute build only for 1st machine, wait till it's
finished, then run script wait till it's finished and then start for
loop for remainig 7, but that does not allow me to fall asleep while
it's still building 1st :) or I have to plan it in advance and build
with much longer one-liner.
Cheers,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2012-11-15 17:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 22:51 [PATCH] scripts/sstate-sysroot-cruft.sh: add simple script to find files in sysroots not tracked by sstate Martin Jansa
2012-10-24 8:10 ` [PATCHv2] " Martin Jansa
2012-10-24 11:15 ` [PATCHv3] " Martin Jansa
2012-11-15 7:30 ` [PATCHv4] " Martin Jansa
2012-11-15 15:25 ` Chris Larson
2012-11-15 16:19 ` Martin Jansa
2012-11-15 16:27 ` Chris Larson
2012-11-15 17:09 ` Martin Jansa
2012-11-15 16:49 ` Paul Eggleton
2012-11-15 17:03 ` Martin Jansa [this message]
2012-11-15 16:34 ` [PATCHv5] " Martin Jansa
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=20121115170340.GD17521@jama.jama.net \
--to=martin.jansa@gmail.com \
--cc=clarson@kergoth.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.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