From: robert.marshall@codethink.co.uk (Robert Marshall)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] CIP Developer update
Date: Thu, 15 Dec 2016 15:22:41 +0000 [thread overview]
Message-ID: <87y3zhcj3y.fsf@codethink.co.uk> (raw)
CIP developer update, we're including outstanding problems as gitlab
issues and there's more information at the issue links.
CIP
- On retrieving build artifacts - we still have issues here. Is it
the VM? have other cip-kernelci users seen this? We've tried manually
entering other likely sounding URLs but without success.
https://gitlab.com/cip-project/testing/issues/2
- github branches have been created for the frontend repos to allow connections from the host
to the VM, with that fork, bson isn't installing for the
frontend - am investigating.
https://gitlab.com/cip-project/testing/issues/3
LAVA
We have created a VM server for LAVA testing; we're trying to get LAVA2
tests to run - it currently doesn't see available devices.
https://gitlab.com/cip-project/testing/issues/4
There'll be a face 2 face discussion between the developers tomorrow to
address the current issues
Robert
next reply other threads:[~2016-12-15 15:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 15:22 Robert Marshall [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-22 15:43 [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=87y3zhcj3y.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