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-2021-09-28-v5.15-rc1)
Date: Tue, 28 Sep 2021 12:16:26 -0700 (PDT) [thread overview]
Message-ID: <61536a0a.1c69fb81.b2857.9e24@mx.google.com> (raw)
renesas/next v4l2-compliance on uvcvideo: 2 runs, 1 regressions (renesas-next-2021-09-28-v5.15-rc1)
Regressions Summary
-------------------
platform | arch | lab | compiler | defconfig | regressions
----------------+-------+---------------+----------+-----------+------------
mt8173-elm-hana | arm64 | lab-collabora | gcc-8 | defconfig | 1
Details: https://kernelci.org/test/job/renesas/branch/next/kernel/renesas-next-2021-09-28-v5.15-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-2021-09-28-v5.15-rc1
URL: https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git
SHA: a462ac13da67252c742a2c044b302f37eae9d089
Test suite revisions:
v4l2-compliance
URL: git://linuxtv.org/v4l-utils.git
SHA: 05a468e033af0e4c775aaa10fe4d02c45de698ae
Test Regressions
----------------
platform | arch | lab | compiler | defconfig | regressions
----------------+-------+---------------+----------+-----------+------------
mt8173-elm-hana | arm64 | lab-collabora | gcc-8 | defconfig | 1
Details: https://kernelci.org/test/plan/id/615357c326f08fab0099a31f
Results: 1 PASS, 1 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/next/renesas-next-2021-09-28-v5.15-rc1/arm64/defconfig/gcc-8/lab-collabora/v4l2-compliance-uvc-mt8173-elm-hana.txt
HTML log: https://storage.kernelci.org//renesas/next/renesas-next-2021-09-28-v5.15-rc1/arm64/defconfig/gcc-8/lab-collabora/v4l2-compliance-uvc-mt8173-elm-hana.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/buster-v4l2/20210913.0/arm64/rootfs.cpio.gz
* v4l2-compliance-uvc.device-presence: https://kernelci.org/test/case/id/615357c326f08fab0099a321
failing since 14 days (last pass: renesas-next-2021-08-12-v5.14-rc1, first fail: v5.15-rc1-39-gcbbd8f16ae1c)
2021-09-28T17:58:20.558809 / #
2021-09-28T17:58:20.561189
2021-09-28T17:58:20.664626 / # #
2021-09-28T17:58:20.667099 #
2021-09-28T17:58:20.769445 / # export SHELL=/bin/sh
2021-09-28T17:58:20.772528 export SHELL=/bin/sh
2021-09-28T17:58:20.874217 / # . /lava-4596911/environment
2021-09-28T17:58:20.876318 . /lava-4596911/environment
2021-09-28T17:58:20.978177 / # /lava-4596911/bin/lava-test-runner /lava-4596911/0
2021-09-28T17:58:20.980786 /lava-4596911/bin/lava-test-runner /lava-4596911/0
... (7 line(s) more)
reply other threads:[~2021-09-28 19:16 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=61536a0a.1c69fb81.b2857.9e24@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