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: 2 runs, 3 regressions (renesas-devel-2021-07-19-v5.14-rc2)
Date: Mon, 19 Jul 2021 15:32:50 -0700 (PDT) [thread overview]
Message-ID: <60f5fd92.1c69fb81.22357.f096@mx.google.com> (raw)
renesas/master v4l2-compliance on uvcvideo: 2 runs, 3 regressions (renesas-devel-2021-07-19-v5.14-rc2)
Regressions Summary
-------------------
platform | arch | lab | compiler | defconfig | regressions
----------------+-------+---------------+----------+-----------+------------
mt8173-elm-hana | arm64 | lab-collabora | gcc-8 | defconfig | 3
Details: https://kernelci.org/test/job/renesas/branch/master/kernel/renesas-devel-2021-07-19-v5.14-rc2/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-2021-07-19-v5.14-rc2
URL: https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git
SHA: 2f3bebb9dc31fbb1e815f63cf3f61763f7d1d8f9
Test suite revisions:
v4l2-compliance
URL: git://linuxtv.org/v4l-utils.git
SHA: 6ffc5248dede6285d76c5ec5680c316f68ff98ca
Test Regressions
----------------
platform | arch | lab | compiler | defconfig | regressions
----------------+-------+---------------+----------+-----------+------------
mt8173-elm-hana | arm64 | lab-collabora | gcc-8 | defconfig | 3
Details: https://kernelci.org/test/plan/id/60f5e3e423d4d000c3116112
Results: 45 PASS, 10 FAIL, 0 SKIP
Full config: defconfig
Compiler: gcc-8 (aarch64-linux-gnu-gcc (Debian 8.3.0-2) 8.3.0)
Plain log: https://storage.kernelci.org//renesas/master/renesas-devel-2021-07-19-v5.14-rc2/arm64/defconfig/gcc-8/lab-collabora/v4l2-compliance-uvc-mt8173-elm-hana.txt
HTML log: https://storage.kernelci.org//renesas/master/renesas-devel-2021-07-19-v5.14-rc2/arm64/defconfig/gcc-8/lab-collabora/v4l2-compliance-uvc-mt8173-elm-hana.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/buster-v4l2/20210709.0/arm64/rootfs.cpio.gz
* v4l2-compliance-uvc.Format-ioctls-Input-0.VIDIOC_S_FMT: https://kernelci.org/test/case/id/60f5e3e423d4d000c311612a
failing since 5 days (last pass: renesas-devel-2021-06-22-v5.13-rc7, first fail: renesas-devel-2021-07-13-v5.14-rc1)
2021-07-19T20:42:58.471724 fail: v4l2-test-formats.cpp(358): !colorspace
2021-07-19T20:43:02.094024 <3>[ 23.614793] usb 1-1: Failed to query (SET_CUR) UVC control 10 on unit 2: -32 (exp. 2).
2021-07-19T20:43:02.109938 fail: v4l2-test-formats.cpp(467): testColorspace(!node->is_io_mc, pix.pixelformat, pix.colorspace, pix.ycbcr_enc, pix.quantization)
2021-07-19T20:43:02.113200 test VIDIOC_S_FMT: FAIL
* v4l2-compliance-uvc.Format-ioctls-Input-0.VIDIOC_TRY_FMT: https://kernelci.org/test/case/id/60f5e3e423d4d000c311612b
failing since 5 days (last pass: renesas-devel-2021-06-22-v5.13-rc7, first fail: renesas-devel-2021-07-13-v5.14-rc1)
2021-07-19T20:42:58.416960 fail: v4l2-test-formats.cpp(358): !colorspace
2021-07-19T20:42:58.435406 fail: v4l2-test-formats.cpp(467): testColorspace(!node->is_io_mc, pix.pixelformat, pix.colorspace, pix.ycbcr_enc, pix.quantization)
2021-07-19T20:42:58.439023 test VIDIOC_TRY_FMT: FAIL
* v4l2-compliance-uvc.Format-ioctls-Input-0.VIDIOC_G_FMT: https://kernelci.org/test/case/id/60f5e3e423d4d000c311612c
failing since 5 days (last pass: renesas-devel-2021-06-22-v5.13-rc7, first fail: renesas-devel-2021-07-13-v5.14-rc1)
2021-07-19T20:42:58.363754 fail: v4l2-test-formats.cpp(358): !colorspace
2021-07-19T20:42:58.381816 fail: v4l2-test-formats.cpp(467): testColorspace(!node->is_io_mc, pix.pixelformat, pix.colorspace, pix.ycbcr_enc, pix.quantization)
2021-07-19T20:42:58.384080 test VIDIOC_G_FMT: FAIL
reply other threads:[~2021-07-20 0:10 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=60f5fd92.1c69fb81.22357.f096@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;
as well as URLs for NNTP newsgroup(s).