public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: robert.marshall@codethink.co.uk (Robert Marshall)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] The Beaglebone black health check supplied in b@d 0.9.1 will no longer run
Date: Mon, 12 Jun 2017 11:34:22 +0100	[thread overview]
Message-ID: <877f0hbikx.fsf@ctlt579.codethink.co.uk> (raw)

The 0.9.1 release of b at d contains a health check for the beaglebone
black which uses various build artifacts on the linaro website at:

http://snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/4

this directory has been moved and the files are now at

http://snapshots.linaro.org/components/lava/standard/debian/jessie/armhf/1

If you have the Vagrant install you will need to change the suggested
test at tests/bbb_debian_ramdisk_test.yaml to reflect the new location
and edit the BBB health check if you have already installed that.

    https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptestingboardatdesksingledevsetup#configure-the-lava-health-check-jobs-for-both-devices

bbb_debian_local.yaml makes one reference to the linaro location which
will also need changing if you use that file in association with
lava-tool.

    https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptestingreferencetestcases#test-5use-lava-tool-utility

The issue https://gitlab.com/cip-project/cip-testing/testing/issues/103
has been created to track this issue.

We intend to update the git repository and release a new provisioned box
later this week to resolve this issue.

Robert

             reply	other threads:[~2017-06-12 10:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-12 10:34 Robert Marshall [this message]
2017-06-13 12:41 ` [cip-dev] The Beaglebone black health check supplied in b@d 0.9.1 will no longer run Robert Marshall

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=877f0hbikx.fsf@ctlt579.codethink.co.uk \
    --to=robert.marshall@codethink.co.uk \
    --cc=cip-dev@lists.cip-project.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