All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/3] Fix SDK downloads forbuilds
Date: Mon, 18 Jan 2016 15:45:07 +0200	[thread overview]
Message-ID: <cover.1453124453.git.ed.bartosh@linux.intel.com> (raw)

Hi,

Artifacts could not be downloaded for a build as they were not being listed.
It was not possible to download them manually either, as the artifact download
code was broken for SDK artifacts produced by command line builds.

Fix how toaster.bbclass hooks onto bitbake's build tasks, so that the SDK
artifacts are picked up after do_populate_sdk runs.

Fix Toaster code for returning SDK artifacts in HTTP responses.

Changes since b53df3c (toaster-next) are in
git://git.yoctoproject.org/poky-contrib, elliot/toaster/sdk_artifacts-7603
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=elliot/toaster/sdk_artifacts-7603

NB one of the commits on this branch (fbc2024) has been submitted to oe-core:
http://lists.openembedded.org/pipermail/openembedded-core/2016-January/115366.html
This patch set contains the other commits on the branch.

Related bug: https://bugzilla.yoctoproject.org/show_bug.cgi?id=7603

To test:

1. Ensure that your database has no build artifacts in it, either by
removing the database, clearing the relevant table with SQL via the command line
(delete from orm_buildartifact), or removing the objects via the Django shell
(orm.models.BuildArtifact.objects.all().delete()).

Note that the current behaviour, where we only associate SDK artifacts with the
first build which produces them, has not been modified. So if you have already
run a build and have files in tmp/deploy/sdk associated with it, subsequent
builds will not be associated with those files.

2. Start a new build from the command line or Toaster, invoking the populate_sdk
target:

# command line
bitbake -c populate_sdk core-image-minimal

# Toaster (NB you must use the "Local" release)
run a build like "core-image-minimal:populate_sdk"

3. View the build dashboard for the build when it completes and ensure it
contains an "Other artifacts" section, as shown in the bug report.

4. Click on one of the "Other artifact" links and ensure that the artifact
downloads correctly.

As this code slightly modifies all other artifact downloads, you could also
check downloads for the following, too:

* cooker logs
* task logs
* image files
* licence manifests


The following changes since commit d1cdf28a40489c9d730dfed3a48e67cb34e8890b:

  toaster: tests Remove symlinks from toasteruitest folder (2016-01-18 15:23:51 +0200)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib ed/toaster/submit/elliot/toaster/sdk_artifacts-7603
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=ed/toaster/submit/elliot/toaster/sdk_artifacts-7603

Elliot Smith (3):
  toaster: toasterui: listen for bb.event.MetadataEvent
  toaster: toasterui: log OSErrorException metadata events
  toaster: toastergui: make artifact download more robust

 lib/bb/ui/toasterui.py                             |  5 +-
 .../toastergui/templates/unavailable_artifact.html | 13 ++-
 lib/toaster/toastergui/views.py                    | 97 +++++++++-------------
 3 files changed, 51 insertions(+), 64 deletions(-)

--
Regards,
Ed



             reply	other threads:[~2016-01-18 15:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18 13:45 Ed Bartosh [this message]
2016-01-18 13:45 ` [PATCH 1/3] toaster: toasterui: listen for bb.event.MetadataEvent Ed Bartosh
2016-01-18 13:45 ` [PATCH 2/3] toaster: toasterui: log OSErrorException metadata events Ed Bartosh
2016-01-18 13:45 ` [PATCH 3/3] toaster: toastergui: make artifact download more robust Ed Bartosh
2016-01-18 22:09 ` [PATCH 0/3] Fix SDK downloads forbuilds Richard Purdie
2016-01-18 22:09   ` [bitbake-devel] " Richard Purdie

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=cover.1453124453.git.ed.bartosh@linux.intel.com \
    --to=ed.bartosh@linux.intel.com \
    --cc=bitbake-devel@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 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.