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, 1 regressions (renesas-devel-2022-05-16-v5.18-rc7)
Date: Mon, 16 May 2022 09:28:45 -0700 (PDT) [thread overview]
Message-ID: <62827bbd.1c69fb81.ae401.1939@mx.google.com> (raw)
renesas/master v4l2-compliance on uvcvideo: 2 runs, 1 regressions (renesas-devel-2022-05-16-v5.18-rc7)
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/master/kernel/renesas-devel-2022-05-16-v5.18-rc7/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-2022-05-16-v5.18-rc7
URL: https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git
SHA: f35c24489921b1d4963dbb55053b97fb0e53f471
Test suite revisions:
v4l2-compliance
URL: git://linuxtv.org/v4l-utils.git
SHA: 163144712a46229f3476b04f6c0037c4b7f00299
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/62826dae7bfcda1a378f571f
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-2022-05-16-v5.18-rc7/arm64/defconfig+arm64-chromebook/gcc-10/lab-collabora/v4l2-compliance-uvc-mt8173-elm-hana.txt
HTML log: https://storage.kernelci.org//renesas/master/renesas-devel-2022-05-16-v5.18-rc7/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/20220513.0/arm64/rootfs.cpio.gz
* v4l2-compliance-uvc.login: https://kernelci.org/test/case/id/62826dae7bfcda1a378f5720
new failure (last pass: renesas-devel-2022-05-09-v5.18-rc6)
reply other threads:[~2022-05-16 16:28 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=62827bbd.1c69fb81.ae401.1939@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.