From: "kernelci.org bot" <bot@kernelci.org>
To: linux-renesas-soc@vger.kernel.org, kernelci-results@groups.io
Subject: renesas/next v4l2-compliance on uvcvideo: 2 runs, 1 regressions (renesas-next-2023-01-24-v6.2-rc1)
Date: Tue, 24 Jan 2023 06:41:59 -0800 (PST) [thread overview]
Message-ID: <63cfee37.170a0220.6e45a.c504@mx.google.com> (raw)
renesas/next v4l2-compliance on uvcvideo: 2 runs, 1 regressions (renesas-next-2023-01-24-v6.2-rc1)
Regressions Summary
-------------------
platform | arch | lab | compiler | defconfig | regressions
----------------+-------+---------------+----------+----------------------------+------------
mt8173-elm-hana | arm64 | lab-collabora | gcc-10 | defconfig+arm64-chromebook | 1
Details: https://kernelci.org/test/job/renesas/branch/next/kernel/renesas-next-2023-01-24-v6.2-rc1/plan/v4l2-compliance-uvc/
V4L2 Compliance on the uvcvideo driver.
This test ran "v4l2-compliance -s" from v4l-utils:
https://www.linuxtv.org/wiki/index.php/V4l2-utils
See each detailed section in the report below to find out the git URL and
particular revision that was used to build the test binaries.
Tree: renesas
Branch: next
Describe: renesas-next-2023-01-24-v6.2-rc1
URL: https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git
SHA: 29fea68a8aaad7d0cab07f538d02aa03ad75fb48
Test suite revisions:
v4l2-compliance
URL: git://linuxtv.org/v4l-utils.git
SHA: 2a982f825cb772419a7fe122c277d461cef346f8
Test Regressions
----------------
platform | arch | lab | compiler | defconfig | regressions
----------------+-------+---------------+----------+----------------------------+------------
mt8173-elm-hana | arm64 | lab-collabora | gcc-10 | defconfig+arm64-chromebook | 1
Details: https://kernelci.org/test/plan/id/63cfddc6e3ccab4e1c915eee
Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: defconfig+arm64-chromebook
Compiler: gcc-10 (aarch64-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//renesas/next/renesas-next-2023-01-24-v6.2-rc1/arm64/defconfig+arm64-chromebook/gcc-10/lab-collabora/v4l2-compliance-uvc-mt8173-elm-hana.txt
HTML log: https://storage.kernelci.org//renesas/next/renesas-next-2023-01-24-v6.2-rc1/arm64/defconfig+arm64-chromebook/gcc-10/lab-collabora/v4l2-compliance-uvc-mt8173-elm-hana.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye-v4l2/20221216.0/arm64/rootfs.cpio.gz
* v4l2-compliance-uvc.login: https://kernelci.org/test/case/id/63cfddc6e3ccab4e1c915eef
new failure (last pass: renesas-next-2022-12-26-v6.2-rc1)
reply other threads:[~2023-01-24 14:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=63cfee37.170a0220.6e45a.c504@mx.google.com \
--to=bot@kernelci.org \
--cc=kernelci-results@groups.io \
--cc=linux-renesas-soc@vger.kernel.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.