All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre McCurdy <armccurdy@gmail.com>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2] Avoid build failures due to setscene errors
Date: Tue, 29 Aug 2017 13:38:02 -0700	[thread overview]
Message-ID: <CAJ86T=VajsxSGRakyVVmTZcEWwwLaVZxKpcsE+ZU75bGrsUkbQ@mail.gmail.com> (raw)
In-Reply-To: <cover.1504036763.git.pkj@axis.com>

On Tue, Aug 29, 2017 at 1:00 PM, Peter Kjellerstedt
<peter.kjellerstedt@axis.com> wrote:
> Occasionally, we see errors on our autobuilders where a setscene task
> fails to retrieve a file from our global sstate cache. It typically
> looks something like this:
>
> WARNING: zip-3.0-r2 do_populate_sysroot_setscene: Failed to fetch URL
> file://66/sstate:zip:core2-64-poky-linux:3.0:r2:core2-64:3:\
> 66832b8c4e7babe0eac9d9579d1e2b6a_populate_sysroot.tgz;\
> downloadfilename=66/sstate:zip:core2-64-poky-linux:3.0:r2:core2-64:3:\
> 66832b8c4e7babe0eac9d9579d1e2b6a_populate_sysroot.tgz, attempting
> MIRRORS if available
> ERROR: zip-3.0-r2 do_populate_sysroot_setscene: Fetcher failure:
> Unable to find file
> file://66/sstate:zip:core2-64-poky-linux:3.0:r2:core2-64:3:\
> 66832b8c4e7babe0eac9d9579d1e2b6a_populate_sysroot.tgz;\
> downloadfilename=66/sstate:zip:core2-64-poky-linux:3.0:r2:core2-64:3:\
> 66832b8c4e7babe0eac9d9579d1e2b6a_populate_sysroot.tgz anywhere. The
> paths that were searched were:
>     /home/pkj/.openembedded/sstate-cache

To trigger this, do you have SSTATE_MIRRORS pointing to
"/home/pkj/.openembedded/sstate-cache" and SSTATE_DIR pointed
somewhere else? Or are they both pointing to the same local directory?
Or something else?

> ERROR: zip-3.0-r2 do_populate_sysroot_setscene: No suitable staging
> package found
> WARNING: Setscene task
> (meta/recipes-extended/zip/zip_3.0.bb:do_populate_sysroot_setscene)
> failed with exit code '1' - real task will be run instead
>


  parent reply	other threads:[~2017-08-29 20:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-29 20:00 [PATCH 0/2] Avoid build failures due to setscene errors Peter Kjellerstedt
2017-08-29 20:00 ` [PATCH 1/2] bitbake: fetch2: Allow Fetch.download() to warn instead of error Peter Kjellerstedt
2017-08-29 20:00 ` [PATCH 2/2] sstate.bbclass: Do not cause build failures due to setscene errors Peter Kjellerstedt
2017-08-29 20:04 ` ✗ patchtest: failure for Avoid " Patchwork
2017-08-29 20:25   ` Peter Kjellerstedt
2017-08-29 22:35     ` Philip Balister
2017-08-30  7:41       ` Peter Kjellerstedt
2017-08-29 20:38 ` Andre McCurdy [this message]
2017-08-29 20:59   ` [PATCH 0/2] " Peter Kjellerstedt
2017-08-29 21:49     ` Richard Purdie
2017-08-30  6:44       ` Peter Kjellerstedt
2017-08-30  7:54         ` Martin Jansa
2019-11-29 16:48           ` Martin Jansa
2020-01-09 12:26             ` Ricardo Ribalda Delgado
2017-08-30  8:02         ` Richard Purdie
2017-08-30  9:52           ` Peter Kjellerstedt
2017-08-29 22:03     ` Andre McCurdy
2017-08-30  9:55       ` Peter Kjellerstedt

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='CAJ86T=VajsxSGRakyVVmTZcEWwwLaVZxKpcsE+ZU75bGrsUkbQ@mail.gmail.com' \
    --to=armccurdy@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=peter.kjellerstedt@axis.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 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.