From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Kernel maintenance and CIP testing report weeks 28, 29 and 30
Date: Tue, 1 Aug 2017 16:10:41 +0100 [thread overview]
Message-ID: <598099F1.7010908@codethink.co.uk> (raw)
Dear CIP friends,
this is the report of the major actions related with those activities
led by Codethink Ltd. Some of the reported topics were already
communicated through this mailing list.
++ Kernel maintenance
1. Backported of the basic support for the Renesas board (family) has
been merged.
2. The first round of kernel features review has been provided. Some
feedback is still pending. Ben H. participated in the CIP TSC bi-weekly
call.
3. Now we need to define the next steps in the kernel maintenance front.
4. As usual, Ben H. is contributing to the upstream 4.4 LTS cycle.
++ CIP Testing
1. E-mail configuration in LAVA is done. Robert Marshall is publishing
the outcome of the basic health checks in the cip-testing-results
mailing list. Feel free to join:
https://lists.cip-project.org/mailman/listinfo/cip-testing-results The
documentation for CIP members to send reports through mail is work in
progress. https://gitlab.com/cip-project/cip-testing/testing/issues/102
2. B at D now works on a W10 machine with little additional configurations.
Both, Windows and Linux users share the same installations and
configuration steps except when specifically mentioned. Waiting to
receive feedback from Members.
https://gitlab.com/cip-project/cip-testing/testing/issues/106
3. A change in git://git.linaro.org/qa/test-definitions.git had a major
impact in B at D. It has been fixed now.
https://gitlab.com/cip-project/cip-testing/testing/issues/116
4. There is progress in using B at D behind a web proxy.
https://gitlab.com/cip-project/cip-testing/testing/issues/99
5. Robert has started the trials to update the LAVA version shipped with
B at D. It includes several fixed to issues we are facing plus several
improvements we will need in the near future.
https://gitlab.com/cip-project/cip-testing/testing/issues/114
6. Other topics
* Some weeks ago we reported to the LAVA team an issue that has already
been fixed upstream. Another good reason for updating LAVA.
https://gitlab.com/cip-project/cip-testing/testing/issues/84
* Several issues has been fixed like tickets #112, #92
* As reported, new repositories has been created and populated.
https://gitlab.com/cip-project/cip-testing/testing/issues/100
** We are starting to populate CIP-kernel-test-logs repository as a
first step towards publishing the "passed test" logs in a public repo in
order to compare the logs from tests done by other Members.
* There is no room for celebrating the CIP workshop at ELCE during the
even. We will need to include it the previous day, right after the CIP
TSC f2f meeting.
* At least Agustin B.B. and Ben H. will attend to ELCE.
Best Regards
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk
next reply other threads:[~2017-08-01 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 15:10 Agustin Benito Bethencourt [this message]
2017-08-01 15:34 ` [cip-dev] Kernel maintenance and CIP testing report weeks 28, 29 and 30 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=598099F1.7010908@codethink.co.uk \
--to=agustin.benito@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