From: Tzung-Bi Shih <tzungbi@kernel.org>
To: "kernelci.org bot" <bot@kernelci.org>
Cc: kernel-build-reports@lists.linaro.org,
kernelci-results@groups.io, chrome-platform@lists.linux.dev,
eballetbo@gmail.com, bleung@chromium.org, groeck@chromium.org,
pmalani@chromium.org
Subject: Re: chrome-platform/for-kernelci cros-ec: 10 runs, 2 regressions (v6.4-rc1-1-gc9f9c6c875d14)
Date: Mon, 15 May 2023 15:21:50 +0800 [thread overview]
Message-ID: <ZGHdjqL9Nvg3eTBt@google.com> (raw)
In-Reply-To: <645d7c69.170a0220.4056f.f4f3@mx.google.com>
On Thu, May 11, 2023 at 04:38:17PM -0700, kernelci.org bot wrote:
> chrome-platform/for-kernelci cros-ec: 10 runs, 2 regressions (v6.4-rc1-1-gc9f9c6c875d14)
>
> Regressions Summary
> -------------------
>
> platform | arch | lab | compiler | defconfig | regressions
> -----------------------------+-------+---------------+----------+----------------------------+------------
> mt8183-kukui-...uniper-sku16 | arm64 | lab-collabora | gcc-10 | defconfig+arm64-chromebook | 1
> mt8192-asurada-spherion-r0 | arm64 | lab-collabora | gcc-10 | defconfig+arm64-chromebook | 1
>
> Details: https://kernelci.org/test/job/chrome-platform/branch/for-kernelci/kernel/v6.4-rc1-1-gc9f9c6c875d14/plan/cros-ec/
>
> Test: cros-ec
> Tree: chrome-platform
> Branch: for-kernelci
> Describe: v6.4-rc1-1-gc9f9c6c875d14
> URL: https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git
> SHA: c9f9c6c875d14a107dabcf4579fcab95ed30af31
>
> Test suite revisions:
> cros-ec-tests
> URL: https://github.com/kernelci/cros-ec-tests.git
> SHA: fad9423ae3c64bfd48c207de34a1177000d45fa8
The 2 regressions are persistent after chrome-platform rebased to v6.4-rc1.
I am investigating them.
next prev parent reply other threads:[~2023-05-15 7:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 23:38 chrome-platform/for-kernelci cros-ec: 10 runs, 2 regressions (v6.4-rc1-1-gc9f9c6c875d14) kernelci.org bot
2023-05-15 7:21 ` Tzung-Bi Shih [this message]
2023-05-19 3:00 ` Tzung-Bi Shih
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=ZGHdjqL9Nvg3eTBt@google.com \
--to=tzungbi@kernel.org \
--cc=bleung@chromium.org \
--cc=bot@kernelci.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 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.