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: 4 runs, 1 regressions (renesas-next-2023-03-16-v6.3-rc1)
Date: Thu, 16 Mar 2023 11:43:35 -0700 (PDT) [thread overview]
Message-ID: <64136357.170a0220.38fd4.021d@mx.google.com> (raw)
renesas/next v4l2-compliance on uvcvideo: 4 runs, 1 regressions (renesas-next-2023-03-16-v6.3-rc1)
Regressions Summary
-------------------
platform | arch | lab | compiler | defconfig | regressions
---------------------------+-------+---------------+----------+----------------------------+------------
mt8192-asurada-spherion-r0 | arm64 | lab-collabora | gcc-10 | defconfig+arm64-chromebook | 1
Details: https://kernelci.org/test/job/renesas/branch/next/kernel/renesas-next-2023-03-16-v6.3-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-03-16-v6.3-rc1
URL: https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git
SHA: 8184e7e383be876199a3be519c067b40143d8ab8
Test suite revisions:
v4l2-compliance
URL: git://linuxtv.org/v4l-utils.git
SHA: c7823a3f5f8846561d91e7ae77fea82fab63fff1
Test Regressions
----------------
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/6413504cde88a5e1ed8c86de
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-03-16-v6.3-rc1/arm64/defconfig+arm64-chromebook/gcc-10/lab-collabora/v4l2-compliance-uvc-mt8192-asurada-spherion-r0.txt
HTML log: https://storage.kernelci.org//renesas/next/renesas-next-2023-03-16-v6.3-rc1/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/20230303.0/arm64/rootfs.cpio.gz
* v4l2-compliance-uvc.login: https://kernelci.org/test/case/id/6413504cde88a5e1ed8c86df
new failure (last pass: renesas-next-2023-03-06-v6.3-rc1)
reply other threads:[~2023-03-16 18:43 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=64136357.170a0220.38fd4.021d@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox