From: Muhammad Usama Anjum <usama.anjum@collabora.com>
To: Todd Kjos <tkjos@google.com>
Cc: Muhammad Usama Anjum <usama.anjum@collabora.com>,
Mark Brown <broonie@kernel.org>,
kernelci@lists.linux.dev,
Viktor Martensson <vmartensson@google.com>,
Betty Zhou <bettyzhou@google.com>,
Denys Fedoryshchenko <denys.f@collabora.com>,
Gustavo Padovan <gus@collabora.com>,
Shreeya Patel <shreeya.patel@collabora.com>,
Helen Mae Koike Fornazier <helen.koike@collabora.com>
Subject: Re: new branch + more recent gcc?
Date: Wed, 17 Jul 2024 15:54:00 +0500 [thread overview]
Message-ID: <592bc672-ea3d-4e57-9db9-a952957bfef8@collabora.com> (raw)
In-Reply-To: <CAHRSSExNqUG8fTi=A2BNjqmxP=NicRqF5z1_sQNR5-BEW31=RQ@mail.gmail.com>
Hi Todd,
All android build configurations have been enabled in new KernelCI. We have
also enabled boot testing on some configurations. We have already started
getting results. We have the grafana dashboard:
https://grafana.kernelci.org/d/OKXc44EIz/wip3a-koike?orgId=1&var-origin=maestro&var-tree=android&var-branch=All&var-test_path_regex=%25&var-platform=%25&var-config=%25&var-datasource=cdmoe4lcafu2od
It is still WIP, but you can see some results data there. We also have a
supplier in the KernelCI Foundation implementing our new Web Dashboard. We
will have a first version by LPC.
We are eager to get feedback from the community. I added Shreeya and Helen
to the CC. Shreeya is overlooking the quality of the data and cataloging
things we need to improve on. And Helen has been driving the implementation
of this grafana based dashboards and improving how we can create issues to
track failures. We would be happy to hear feedback from you or even jump in
a call to present things more in depth.
Thanks,
Usama
On 7/16/24 8:18 PM, Todd Kjos wrote:
> On Tue, Jul 16, 2024 at 2:40 AM Muhammad Usama Anjum
> <usama.anjum@collabora.com> wrote:
>>
>> Hi Todd,
>>
>> It seems like some branches in android repository have been deprecated. We
>> are thinking of removing them from the KernelCI. Is it okay to do so? Or do
>> you want us to continually running tests on these deprecated branches for a
>> little while? I'm not sure about the deprecation schedule for these.
>>
>> android_4.9-p, android_4.9-q-release, android_4.14-p,
>> android_4.14-q-release, android_4.14-stable, android_4.19-q-release
>
> Yes, all of these can be removed. android-4.14-stable too.
I've removed all of these.
>
>>
>> Thanks,
>> Usama
>>
--
BR,
Muhammad Usama Anjum
next prev parent reply other threads:[~2024-07-17 10:54 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 22:41 Please add new Android branches Todd Kjos
2023-07-11 11:57 ` Guillaume Tucker
[not found] ` <CAHRSSEzMo=-eS8KRqHjSMcBqWCsK2mU4zWg=5KFYx2XyL29Z0w@mail.gmail.com>
2023-09-05 17:18 ` Todd Kjos
2023-09-06 18:46 ` Guillaume Tucker
2023-09-06 19:50 ` Todd Kjos
2023-09-19 22:54 ` Todd Kjos
2023-09-19 23:02 ` Nick Desaulniers
2023-09-19 23:12 ` Todd Kjos
2023-09-19 23:19 ` Nick Desaulniers
2023-09-20 0:12 ` Todd Kjos
2023-09-20 16:57 ` Nick Desaulniers
2023-09-25 8:17 ` Guillaume Tucker
2023-09-25 15:28 ` Nick Desaulniers
2023-09-25 8:23 ` Guillaume Tucker
2023-09-25 15:17 ` Todd Kjos
2023-10-17 20:42 ` Todd Kjos
2023-11-02 22:11 ` Todd Kjos
2023-11-04 1:57 ` Denys Fedoryshchenko
2023-11-06 18:03 ` Todd Kjos
2023-11-07 8:26 ` Guillaume Tucker
2023-11-10 21:14 ` Todd Kjos
2024-07-01 17:03 ` new branch + more recent gcc? Todd Kjos
2024-07-01 17:05 ` Todd Kjos
2024-07-01 17:27 ` Todd Kjos
2024-07-02 13:12 ` Mark Brown
2024-07-02 15:45 ` Todd Kjos
2024-07-04 6:09 ` Muhammad Usama Anjum
2024-07-09 17:02 ` Todd Kjos
2024-07-09 17:38 ` Denys Fedoryshchenko
2024-07-11 17:20 ` Todd Kjos
2024-07-16 9:39 ` Muhammad Usama Anjum
2024-07-16 15:18 ` Todd Kjos
2024-07-17 10:54 ` Muhammad Usama Anjum [this message]
2024-02-03 18:43 ` Please add new Android branches Todd Kjos
2024-02-05 6:03 ` Denys Fedoryshchenko
2024-02-09 19:38 ` Todd Kjos
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=592bc672-ea3d-4e57-9db9-a952957bfef8@collabora.com \
--to=usama.anjum@collabora.com \
--cc=bettyzhou@google.com \
--cc=broonie@kernel.org \
--cc=denys.f@collabora.com \
--cc=gus@collabora.com \
--cc=helen.koike@collabora.com \
--cc=kernelci@lists.linux.dev \
--cc=shreeya.patel@collabora.com \
--cc=tkjos@google.com \
--cc=vmartensson@google.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).