All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Kristian Amlie <kristian.amlie@mender.io>,
	"poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: SSTATE_MIRRORS not working?
Date: Fri, 13 Jan 2017 10:41:32 +0000	[thread overview]
Message-ID: <1484304092.4367.248.camel@linuxfoundation.org> (raw)
In-Reply-To: <e5ed867c-cb26-466c-694f-65d60254cd60@mender.io>

On Fri, 2017-01-13 at 09:50 +0100, Kristian Amlie wrote:
> For some time now, I've had the problem that SSTATE_MIRRORS does not
> work properly for me. I can see that it downloads lots of packages
> from the cache, but once the setscene stage is over, and runqueue
> begins, it starts the whole build from scratch regardless.
> 
> This used to work for me before, it would only run a small subset of
> the tasks locally, taking full advantage of the cache, so I'm fairly
> certain my setup is correct. For me it broke maybe six weeks ago or
> so (master branch).
> 
> I realize this question may be more appropriate for bitbake-devel,
> and I can provide more details, but I thought I'd just hear if
> anybody else has experienced the same, before I go digging.

Which SSTATE_MIRRORS are you using?

The build logs should show what is being rebuilt. The autobuilder does
reuse sstate during its builds and we'd likely have noticed long build
times if it was completely broken so its likely some mismatch between
your setup and what is in the particular mirror you're using.

Cheers,

Richard


  reply	other threads:[~2017-01-13 10:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-13  8:50 SSTATE_MIRRORS not working? Kristian Amlie
2017-01-13 10:41 ` Richard Purdie [this message]
2017-01-13 12:35   ` Kristian Amlie
2017-01-13 14:58     ` Kristian Amlie
2017-01-13 15:04       ` Joshua Lock

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=1484304092.4367.248.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=kristian.amlie@mender.io \
    --cc=poky@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.