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] cip-dev progress report weeks 20 - 29
Date: Thu, 02 Aug 2018 16:00:26 +0100	[thread overview]
Message-ID: <87y3dozud1.fsf@ctlt579.codethink.co.uk> (raw)
In-Reply-To: <CAEss1E+w1ujdzO8DbkPa7Sm9v8DdUVhg2Tfyy-Pj8peBGXkNmw@mail.gmail.com> (Zoran S.'s message of "Wed, 25 Jul 2018 15:27:58 +0200")

Zoran

Thanks for this.

Zoran S <zoran.stojsavljevic.de@gmail.com> writes:

>> The master of B at D now installs 2018.4 rather the latest from
>>  debian-backports making the tool more resilient to upstream changes
>>  and allowing us to evaluate an upstream change before it goes live.
>
> I absolutely agree with this approach, only I would use the following
> Lava release:
>
> ii  lava-dispatcher
> 2018.5.post1-1+stretch      amd64                   Linaro Automated
> Validation Architecture dispatcher
> ii  lava-server
> 2018.5.post1-1+stretch      all                         Linaro
> Automated Validation Architecture server
>
> Thus making this line in the integration scripts as following:
>
> sudo DEBIAN_FRONTEND=noninteractive apt-get -y install
> lava=2018.5.post1-1+stretch -t stretch-backports
>
> I have tested this release, and with exclusion of minor bugs it works
> very fine (these bugs are also present in 2018.4).

We've stuck with 2018-4 as it has worked but will evaluate newer
versions at appropriate times rather than finding the version has
changed on a fresh provision and potentially having to fix things quickly!

>
> Do NOT use Lava 2018.7 (I guess, it is a mess)!
>
Thanks for this information - I'll see when we get to it!

Robert


> Thank you,
> Zoran
> _______
>
> On Wed, Jul 25, 2018 at 2:31 PM, Robert Marshall
> <robert.marshall@codethink.co.uk> wrote:
>> Hi! Here's a report on the Codethink CIP testing development over the
>> past few weeks.
>>
>> CIP kernel testing
>>
>> - The master of B at D now installs 2018.4 rather the latest from
>>   debian-backports making the tool more resilient to upstream changes
>>   and allowing us to evaluate an upstream change before it goes live.
>>
>> - Also linked to the above the beaglebone black health check now uses an
>>   inline test; this both breaks the reliance upon an upstream test repos
>>   structure and making testing less dependent upon needing an internet connection.
>>
>> - Renesas board - this hardware continued to not give consistent results in B at D
>>   tests so for the moment development has been suspended.
>>
>> - Development has started on using docker containers for B at D - the
>>   kernelci one is up and kernel builds have successfully been uploaded
>>   to it, there is an outstanding issue with retrieving those builds from
>>   the container. Work is also being carried out on the lava docker container.
>>
>> Robert
>> --
>> Robert Marshall, Software Developer                       Codethink Ltd
>> Telephone: +44 7762 840 414       3rd Floor, Dale House, 35 Dale Street
>> https://www.codethink.co.uk/         MANCHESTER, M1 2HF. United Kingdom
>> _______________________________________________
>> cip-dev mailing list
>> cip-dev at lists.cip-project.org
>> https://lists.cip-project.org/mailman/listinfo/cip-dev
>

  reply	other threads:[~2018-08-02 15:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-25 12:31 [cip-dev] cip-dev progress report weeks 20 - 29 Robert Marshall
2018-07-25 13:27 ` Zoran S
2018-08-02 15:00   ` Robert Marshall [this message]
2018-08-03  8:27     ` Zoran S
2018-08-08  7:59     ` Zoran S

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=87y3dozud1.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