All of lore.kernel.org
 help / color / mirror / Atom feed
From: robert.marshall@codethink.co.uk (Robert Marshall)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] CIP update 07 WK 01
Date: Fri, 06 Jan 2017 14:57:18 +0000	[thread overview]
Message-ID: <8760lsdynl.fsf@codethink.co.uk> (raw)
In-Reply-To: <87a8b4e479.fsf@codethink.co.uk> (Robert Marshall's message of "Fri, 06 Jan 2017 12:57:30 +0000")

Apologies, the following item was missed out of the report:

        * build artifacts - we're still unable to retrieve these and get
          404 errors on selecting the link:
              https://gitlab.com/cip-project/testing/issues/2
           

Robert Marshall <robert.marshall@codethink.co.uk> writes:

> * Virtual machine creation for the testing
>   We've created 2 vagrant instances one for kernelci and the other for lava
>   (lava is Debian based and kernelci is ubuntu based) work is in
>   progress on merging these to make developer setup simpler and reduce
>   the memory requirements.
>       https://gitlab.com/cip-project/testing/issues/7
>
> * There's a github branch to allow the host to view the kernelci vm webserver
>   https://github.com/RobertAJMarshall/kernelci-frontend-config/tree/external-http
>   this will be merged with the gitlab repository when
>       https://gitlab.com/cip-project/testing/issues/3
>   has been resolved.
>
> * The DeviceDictionary error 
>       https://gitlab.com/cip-project/testing/issues/5
>   is still outstanding
>
> * Devices have been added to lava VM but are not yet running
>       https://gitlab.com/cip-project/testing/issues/9
>
> * the lava gitlab and the vagrant instance now has been updated 
>   with health check tests and extra documentation.
>   
> * The QEMU health check results in a KVM module not found failure
>       https://gitlab.com/cip-project/testing/issues/8
>
> * Discussions in progress on adding a 'howto'
>   The developers have a document enumerating the steps involved in
>   getting the testing environment up and running, this document will
>   be streamlined and published to the wiki. Meanwhile, we will add the
>   WIP content to the repository so you can follow it.
>
> * Minor additions to the wiki has been made, specially in the kernel
>   maintenance page.
>
> Robert
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

  reply	other threads:[~2017-01-06 14:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-22 15:43 [cip-dev] CIP Developer update Robert Marshall
2017-01-06 12:57 ` [cip-dev] CIP update 07 WK 01 Robert Marshall
2017-01-06 14:57   ` Robert Marshall [this message]
2017-01-20 16:00   ` [cip-dev] CIP update 08 WK 03 Agustin Benito Bethencourt

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=8760lsdynl.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 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.