From: "kernelci.org bot" <bot@kernelci.org>
To: linux-renesas-soc@vger.kernel.org, kernelci-results@groups.io
Subject: renesas/next sleep: 3 runs, 4 regressions (renesas-next-2022-02-02-v5.17-rc1)
Date: Wed, 02 Feb 2022 03:43:12 -0800 (PST) [thread overview]
Message-ID: <61fa6e50.1c69fb81.879b5.ac87@mx.google.com> (raw)
renesas/next sleep: 3 runs, 4 regressions (renesas-next-2022-02-02-v5.17-rc1)
Regressions Summary
-------------------
platform | arch | lab | compiler | defconfig | regressions
--------------------+------+---------------+----------+--------------------+------------
rk3288-rock2-square | arm | lab-collabora | gcc-10 | multi_v7_defconfig | 4
Details: https://kernelci.org/test/job/renesas/branch/next/kernel/renesas-next-2022-02-02-v5.17-rc1/plan/sleep/
Test: sleep
Tree: renesas
Branch: next
Describe: renesas-next-2022-02-02-v5.17-rc1
URL: https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git
SHA: c3b08f12c71900ef2e92cc8f778f3073afe69f4c
Test Regressions
----------------
platform | arch | lab | compiler | defconfig | regressions
--------------------+------+---------------+----------+--------------------+------------
rk3288-rock2-square | arm | lab-collabora | gcc-10 | multi_v7_defconfig | 4
Details: https://kernelci.org/test/plan/id/61fa574f7bc2ec11485d6eeb
Results: 2 PASS, 13 FAIL, 0 SKIP
Full config: multi_v7_defconfig
Compiler: gcc-10 (arm-linux-gnueabihf-gcc (Debian 10.2.1-6) 10.2.1 20210110)
Plain log: https://storage.kernelci.org//renesas/next/renesas-next-2022-02-02-v5.17-rc1/arm/multi_v7_defconfig/gcc-10/lab-collabora/sleep-rk3288-rock2-square.txt
HTML log: https://storage.kernelci.org//renesas/next/renesas-next-2022-02-02-v5.17-rc1/arm/multi_v7_defconfig/gcc-10/lab-collabora/sleep-rk3288-rock2-square.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/bullseye/20220128.0/armhf/rootfs.cpio.gz
* sleep.rtcwake-mem-1: https://kernelci.org/test/case/id/61fa574f7bc2ec11485d6eef
failing since 4 days (last pass: renesas-next-2022-01-25-v5.17-rc1, first fail: renesas-next-2022-01-28-v5.17-rc1)
2022-02-02T10:04:51.349009 rtcwake: assuming RTC uses UTC ...
2022-02-02T10:04:51.392590 rtcwake: read rt<4>[ 15.976671] rtc-hym8563 0-0051: no valid clock/calendar values available
2022-02-02T10:04:51.393155 c time failed: Invalid argument
2022-02-02T10:04:51.393987 rtcwake: assuming RTC uses UTC .<4>[ 15.996416] rtc-hym8563 0-0051: no valid clock/calendar values available
2022-02-02T10:04:51.394846 ..
2022-02-02T10:04:51.395289 rtcwake: read rtc time failed: Invalid argument
* sleep.rtcwake-mem-5: https://kernelci.org/test/case/id/61fa574f7bc2ec11485d6ef7
failing since 4 days (last pass: renesas-next-2022-01-25-v5.17-rc1, first fail: renesas-next-2022-01-28-v5.17-rc1)
2022-02-02T10:04:51.444006 rtcwake: assuming RTC uses UTC ...
2022-02-02T10:04:51.488916 <4>[ 16.070593] rtc-hym8563 0-0051: no valid clock/calendar values available
2022-02-02T10:04:51.489459 rtcwake: read rtc time failed: Invalid argument
* sleep.rtcwake-mem-4: https://kernelci.org/test/case/id/61fa574f7bc2ec11485d6ef8
failing since 4 days (last pass: renesas-next-2022-01-25-v5.17-rc1, first fail: renesas-next-2022-01-28-v5.17-rc1)
2022-02-02T10:04:51.395986 rtcwake: ass<4>[ 16.014955] rtc-hym8563 0-0051: no valid clock/calendar values available
2022-02-02T10:04:51.396325 uming RTC uses UTC ...
2022-02-02T10:04:51.440720 rtcwake: read rtc time failed: Invalid argument
2022-02-02T10:04:51.441701 =fail>
2022-02-02T10:04:51.442468 rtcwake: assuming RTC uses UTC ...
2022-02-02T10:04:51.442926 rtcwake: read rtc ti<4>[ 16.054483] rtc-hym8563 0-0051: no valid clock/calendar values available
2022-02-02T10:04:51.443308 me failed: Invalid argument
* sleep.rtcwake-mem-2: https://kernelci.org/test/case/id/61fa574f7bc2ec11485d6ef9
failing since 4 days (last pass: renesas-next-2022-01-25-v5.17-rc1, first fail: renesas-next-2022-01-28-v5.17-rc1)
reply other threads:[~2022-02-02 11: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=61fa6e50.1c69fb81.879b5.ac87@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