Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Christopher Larson <kergoth@gmail.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/7] Sanity class clean ups
Date: Wed, 23 May 2012 17:41:18 -0700	[thread overview]
Message-ID: <877EAB77D3024A2AB2CCF0C65D620190@gmail.com> (raw)
In-Reply-To: <cover.1337816265.git.josh@linux.intel.com>

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

This series looks quite sane to me. Nicely done.

-- 
Christopher Larson


On Wednesday, May 23, 2012 at 5:02 PM, Joshua Lock wrote:

> My recent change to the sanity class to warn users when they don't have R/W
> permission to their SSTATE_CACHE directory has caused at least a couple of users
> trouble, including the Yocto project autobuilder.
> 
> I have been unable to reproduce the issue but after discussionwith Elizabeth and
> Chris on #yocto I came up with the following series.
> 
> The series includes a revert my original change as it seems the simple logic has
> severla edge cases. I replace it later in the series with a simple piggy-back
> on the existing check_create_long_filename() call, where I make the suggestion
> of using SSTATE_MIRRORS if that call fails with "Permission denied" when called
> against SSTATE_DIR. This check has been in use for some time and, to the best of
> my knowledge, doesn't trigger invalid failures.
> 
> Thanks to Chris and Elizabeth for pointers as to why this was failing.
> 
> Cheers,
> 
> Joshua
> 
> The following changes since commit e6333825c3482a559a0c0499e17f8f48d3042ddf:
> 
> tune-mips64.inc: Add new tune file for mips64 big-endian (2012-05-20 20:24:37 -0700)
> 
> are available in the git repository at:
> git://git.openembedded.org/openembedded-core-contrib (http://git.openembedded.org/openembedded-core-contrib) josh/sanity
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=josh/sanity
> 
> Joshua Lock (7):
> Revert "sanity.bbclass: check user can read and write to SSTATE_DIR"
> sanity.bbclass: copy the data store and finalise before running
> checks
> sanity.bbclass: data.getVar(VAR, obj, exp) -> obj.getVar(VAR, exp)
> sanity.bbclass: add newline to check_create_long_filename failure
> message
> sanity.bbclass: add extra information when SSTATE_CACHE unusable
> sanity.bbclass: catch an extra exception in
> check_create_long_filename
> sanity.bbclass: check sanity at BuildStarted rather than ConfigParsed
> 
> meta/classes/sanity.bbclass | 153 ++++++++++++++++++++++---------------------
> 1 files changed, 78 insertions(+), 75 deletions(-)
> 
> -- 
> 1.7.7.6
> 
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org (mailto:Openembedded-core@lists.openembedded.org)
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
> 
> 



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

  parent reply	other threads:[~2012-05-24  0:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24  0:02 [PATCH 0/7] Sanity class clean ups Joshua Lock
2012-05-24  0:02 ` [PATCH 1/7] Revert "sanity.bbclass: check user can read and write to SSTATE_DIR" Joshua Lock
2012-05-24  0:02 ` [PATCH 2/7] sanity.bbclass: copy the data store and finalise before running checks Joshua Lock
2012-05-24  0:02 ` [PATCH 3/7] sanity.bbclass: data.getVar(VAR, obj, exp) -> obj.getVar(VAR, exp) Joshua Lock
2012-05-24  0:03 ` [PATCH 4/7] sanity.bbclass: add newline to check_create_long_filename failure message Joshua Lock
2012-05-24  0:03 ` [PATCH 5/7] sanity.bbclass: add extra information when SSTATE_CACHE unusable Joshua Lock
2012-05-24  1:53   ` Joshua Lock
2012-05-24  0:03 ` [PATCH 6/7] sanity.bbclass: catch an extra exception in check_create_long_filename Joshua Lock
2012-05-24  0:03 ` [PATCH 7/7] sanity.bbclass: check sanity at BuildStarted rather than ConfigParsed Joshua Lock
2012-05-24  0:41 ` Christopher Larson [this message]
2012-05-24 18:14 ` [PATCH 0/7] Sanity class clean ups Saul Wold

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=877EAB77D3024A2AB2CCF0C65D620190@gmail.com \
    --to=kergoth@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