From: "kernelci.org bot" <bot@kernelci.org>
To: linux-renesas-soc@vger.kernel.org, kernelci-results@groups.io
Subject: renesas/next usb: 3 runs, 1 regressions (renesas-next-2020-11-30-v5.10-rc1)
Date: Mon, 30 Nov 2020 14:46:36 -0800 (PST) [thread overview]
Message-ID: <5fc5764c.1c69fb81.aa73e.00cc@mx.google.com> (raw)
renesas/next usb: 3 runs, 1 regressions (renesas-next-2020-11-30-v5.10-rc1)
Regressions Summary
-------------------
platform | arch | lab | compiler | defconfig | regressions
----------------+------+---------------+----------+--------------------+------------
imx6q-sabrelite | arm | lab-collabora | gcc-8 | multi_v7_defconfig | 1
Details: https://kernelci.org/test/job/renesas/branch/next/kernel/renesas-next-2020-11-30-v5.10-rc1/plan/usb/
Test: usb
Tree: renesas
Branch: next
Describe: renesas-next-2020-11-30-v5.10-rc1
URL: https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git
SHA: c51a6c86347a721c328a37adf4c3f8892aa10330
Test Regressions
----------------
platform | arch | lab | compiler | defconfig | regressions
----------------+------+---------------+----------+--------------------+------------
imx6q-sabrelite | arm | lab-collabora | gcc-8 | multi_v7_defconfig | 1
Details: https://kernelci.org/test/plan/id/5fc56550dda021c4b3c94cc0
Results: 1 PASS, 1 FAIL, 0 SKIP
Full config: multi_v7_defconfig
Compiler: gcc-8 (arm-linux-gnueabihf-gcc (Debian 8.3.0-2) 8.3.0)
Plain log: https://storage.kernelci.org//renesas/next/renesas-next-2020-11-30-v5.10-rc1/arm/multi_v7_defconfig/gcc-8/lab-collabora/usb-imx6q-sabrelite.txt
HTML log: https://storage.kernelci.org//renesas/next/renesas-next-2020-11-30-v5.10-rc1/arm/multi_v7_defconfig/gcc-8/lab-collabora/usb-imx6q-sabrelite.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/buster/20201130.0/armhf/rootfs.cpio.gz
* usb.usb-presence: https://kernelci.org/test/case/id/5fc56550dda021c4b3c94cc2
failing since 34 days (last pass: renesas-next-2020-09-25-v5.9-rc1, first fail: renesas-next-2020-10-26-v5.10-rc1)
2020-11-30 21:32:37.570000+00:00 [Enter `^Ec?' for help]
2020-11-30 21:32:38.664000+00:00 \0
2020-11-30 21:32:38.665000+00:00
2020-11-30 21:32:38.667000+00:00 U-Boot 2019.01+dfsg-7co6bv2021dev1b1 (Mar 11 2020 - 10:36:34 +0000)
2020-11-30 21:32:38.668000+00:00
2020-11-30 21:32:38.673000+00:00 CPU: Freescale i.MX6Q rev1.2 at 792 MHz
2020-11-30 21:32:38.673000+00:00 Reset cause: POR
2020-11-30 21:32:38.674000+00:00 Board: SABRE Lite
2020-11-30 21:32:38.674000+00:00 I2C: ready
2020-11-30 21:32:38.675000+00:00 DRAM: 1 GiB
... (602 line(s) more)
reply other threads:[~2020-11-30 22:47 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=5fc5764c.1c69fb81.aa73e.00cc@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.