From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Brian Norris <briannorris@chromium.org>
Cc: Mark Brown <broonie@kernel.org>,
kernelci-results@groups.io, "kernelci.org bot" <bot@kernelci.org>,
kernel-build-reports@lists.linaro.org,
chrome-platform@lists.linux.dev, eballetbo@gmail.com,
bleung@chromium.org, groeck@chromium.org, pmalani@chromium.org
Subject: Re: chrome-platform/for-kernelci baseline: 98 runs, 5 regressions (v6.1-rc1-5-g27b86a65cd16)
Date: Tue, 1 Nov 2022 13:32:12 +0800 [thread overview]
Message-ID: <Y2CvXBE414t3sqDC@google.com> (raw)
In-Reply-To: <Y2BcAFf77/JMQxYR@google.com>
On Mon, Oct 31, 2022 at 04:36:32PM -0700, Brian Norris wrote:
[...]
> ...but still, it's kinda sad that we've bothered to set up all this "CI"
> and then nobody paid any attention :( I only noticed because I recently
> subscribed to chrome-platform@lists.linux.dev.
I do notice that the kernelci reported test failures/regressions for
chrome-platform repo. I only raised my hand in some private sessions
instead of public mailing lists.
For now, I only see build results (e.g. [1]) as a signal to move patches
from "for-kernelci" to "for-next" branches; and ignore the regression ones
temporarily.
The LAVA lab "lab-collabora" was setup by Collabora; and it has been
un-maintained for a long while. In order to troubleshooting, I thought
we need to access the LAVA dispatcher and boards (at least from SSH).
But it seems only Collabora folks have the permission to access them.
In either cases, we should figure out a way to make the "CI" back to work.
I will seek for Collabora folks' help.
[1]: https://lore.kernel.org/chrome-platform/63609caf.620a0220.bd35e.9c8e@mx.google.com/T/#u
next prev parent reply other threads:[~2022-11-01 5:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 5:51 chrome-platform/for-kernelci baseline: 98 runs, 5 regressions (v6.1-rc1-5-g27b86a65cd16) kernelci.org bot
2022-10-31 17:40 ` Brian Norris
2022-10-31 19:21 ` Guenter Roeck
2022-10-31 21:37 ` Mark Brown
2022-10-31 22:21 ` Brian Norris
2022-10-31 22:52 ` Mark Brown
2022-10-31 23:36 ` Brian Norris
2022-11-01 5:32 ` Tzung-Bi Shih [this message]
2022-11-01 11:58 ` Mark Brown
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=Y2CvXBE414t3sqDC@google.com \
--to=tzungbi@kernel.org \
--cc=bleung@chromium.org \
--cc=bot@kernelci.org \
--cc=briannorris@chromium.org \
--cc=broonie@kernel.org \
--cc=chrome-platform@lists.linux.dev \
--cc=eballetbo@gmail.com \
--cc=groeck@chromium.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=kernelci-results@groups.io \
--cc=pmalani@chromium.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