From: robert.marshall@codethink.co.uk (Robert Marshall)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] CIP Developer update
Date: Thu, 22 Dec 2016 15:43:53 +0000 [thread overview]
Message-ID: <87a8bo0y12.fsf@codethink.co.uk> (raw)
As before we're including outstanding problems as gitlab
issues - read them for more information!
CIP
- build artifacts - we're still unable to retrieve these.
We have manually installed later versions of chef and worked
around issues with the validation.pem not being available but
are still getting 404 errors.
https://gitlab.com/cip-project/testing/issues/2
bson not installed error
https://gitlab.com/cip-project/testing/issues/3
still being investigated.
LAVA
LAVA2 tests now run, currently working around issues
with a DeviceDictionary error
https://gitlab.com/cip-project/testing/issues/5
Smoke test for QEMU created
Robert
next reply other threads:[~2016-12-22 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 15:43 Robert Marshall [this message]
2017-01-06 12:57 ` [cip-dev] CIP update 07 WK 01 Robert Marshall
2017-01-06 14:57 ` Robert Marshall
2017-01-20 16:00 ` [cip-dev] CIP update 08 WK 03 Agustin Benito Bethencourt
-- strict thread matches above, loose matches on Subject: below --
2016-12-15 15:22 [cip-dev] CIP Developer update 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=87a8bo0y12.fsf@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