From: "kernelci.org bot" <bot@kernelci.org>
To: linux-renesas-soc@vger.kernel.org, kernelci-results@groups.io
Subject: renesas/master v4l2-compliance on uvcvideo: 4 runs, 2 regressions (renesas-devel-2023-06-12-v6.4-rc6)
Date: Mon, 12 Jun 2023 05:54:56 -0700 (PDT) [thread overview]
Message-ID: <648715a0.170a0220.2fb5.608d@mx.google.com> (raw)
renesas/master v4l2-compliance on uvcvideo: 4 runs, 2 regressions (renesas-devel-2023-06-12-v6.4-rc6)
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/renesas/branch/master/kernel/renesas-devel-2023-06-12-v6.4-rc6/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: master
Describe: renesas-devel-2023-06-12-v6.4-rc6
URL: https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git
SHA: eec974413697190538e69788efc6048763f9b64e
Test suite revisions:
v4l2-compliance
URL: git://linuxtv.org/v4l-utils.git
SHA: 52926c1f2f03aebe34d96056e8380ab07c8f512d
Test Regressions
----------------
platform | arch | lab | compiler | defconfig | regressions
-----------------------------+-------+---------------+----------+----------------------------+------------
mt8183-kukui-...uniper-sku16 | arm64 | lab-collabora | gcc-10 | defconfig+arm64-chromebook | 1
Details: https://kernelci.org/test/plan/id/6487063c30a5d157b9306140
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/master/renesas-devel-2023-06-12-v6.4-rc6/arm64/defconfig+arm64-chromebook/gcc-10/lab-collabora/v4l2-compliance-uvc-mt8183-kukui-jacuzzi-juniper-sku16.txt
HTML log: https://storage.kernelci.org//renesas/master/renesas-devel-2023-06-12-v6.4-rc6/arm64/defconfig+arm64-chromebook/gcc-10/lab-collabora/v4l2-compliance-uvc-mt8183-kukui-jacuzzi-juniper-sku16.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye-v4l2/20230527.0/arm64/rootfs.cpio.gz
* v4l2-compliance-uvc.login: https://kernelci.org/test/case/id/6487063c30a5d157b9306141
failing since 33 days (last pass: renesas-devel-2023-04-24-v6.3, first fail: renesas-devel-2023-05-09-v6.4-rc1)
platform | arch | lab | compiler | defconfig | regressions
-----------------------------+-------+---------------+----------+----------------------------+------------
mt8192-asurada-spherion-r0 | arm64 | lab-collabora | gcc-10 | defconfig+arm64-chromebook | 1
Details: https://kernelci.org/test/plan/id/648704bbffe542ddfd30618a
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/master/renesas-devel-2023-06-12-v6.4-rc6/arm64/defconfig+arm64-chromebook/gcc-10/lab-collabora/v4l2-compliance-uvc-mt8192-asurada-spherion-r0.txt
HTML log: https://storage.kernelci.org//renesas/master/renesas-devel-2023-06-12-v6.4-rc6/arm64/defconfig+arm64-chromebook/gcc-10/lab-collabora/v4l2-compliance-uvc-mt8192-asurada-spherion-r0.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye-v4l2/20230527.0/arm64/rootfs.cpio.gz
* v4l2-compliance-uvc.login: https://kernelci.org/test/case/id/648704bbffe542ddfd30618b
failing since 33 days (last pass: renesas-devel-2023-04-24-v6.3, first fail: renesas-devel-2023-05-09-v6.4-rc1)
reply other threads:[~2023-06-12 12:56 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=648715a0.170a0220.2fb5.608d@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.